I am trying to clarify the business logic of updateRecord and client book function. My understanding is
1. for booking, only allow user to input an owner id
2. validation of user input for max 8 bytes integer number (required),
3. updating only for owner field and flag in the database.
However, do I need to allow updating a blank input for unbooking a record? This will provide me for allowing user rebooking a record, which makes more sense to me? Or I misinterpret instruction and should not allow blank input.
old new meaning
blank blank ok; no change
avalue avalue ok; no change
avalue blank ok; unbook
avalue bvalue error; flaged
blank avalue ok; book
This is the scheme I have now. I am near the end of project. Please help me.
In terms of the project, only booking functionality is needed.
[ November 22, 2004: Message edited by: Anton Golovin ]
Thanks. You posted a new question to me. that is leading zero. So far, I treat owner, as well as other field, as string. so leading zero is significant.
So, you mean, in client side, I should take booking literally if following instruction strictly. Unbooking is not part of booking. Therefore, I shouldn't allow a blank input for booking a non-blank owner (ie unbooking). Yes, you are right that sun doesn't require unbook in gui, but it requires to record a owner id as it is, which confused me of when the input is blank.
Originally posted by Andy Zhu:
Hey, Anton: one more about updateRecord in data layer: if an existing record's flag is "booked", and the new input owner is not blank, I guess I should not honor this request even in database layer. What do you think? Do I misunderstand instruction?
Hi, Andy. I think it should be honored in the data layer but not in the business layer.