This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Very sorry second post today. in my database schema, theirs a field called "customer holding this record" and it's description is
"The id value (an 8 digit number) of the customer who has booked this room. If this field is all blanks, the record is available for sale." The question I'm wondering though, is if a room becomes booked using this field, well, how does it become unbooked again? There doesn't seem anyway of removing this customer.
I'm not sure if "unbooking" is necessary. I write to the field when it is booked/reserved and that's the end of it. People have implemented it, but it is beyond the scope of this assignment, so you won't gain anything by doing it. Hope this helps.
Mark O' Sullivan
Joined: Aug 17, 2009
Thanks very much Anne. Good luck with the submission.
I can confirm Anne's remark: unbooking not in scope of this assignment. You may implement it, but it certainly isn't a must (and you won't get extra points for doing it. in fact you may only lose some points if it has a flaw).