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.
I am doing the URLyBird assignment. As part of the room booking 1.I am updting the 'Customer' field in the fb file. 2. In order to avoid rebooking of an already booked room, I make the the alerady booked record uneditable. In this case 'Customer' cell will not editable since it already has a value. 3.In all other cases where 'Customer' field has no values, I make the cell editable. (all the above steps also take in to consideration the 48 hour rule.).
I hope by user you mean CSR. The CSR will be allowed to book only one room at a time. meaning only one row will be allowed to be updated from the the GUI (and all the way down to the DB layer.) I was thinking of
1. making 'Customer' the cell uneditable to prevent accidental rebookings.
2. But now I am thinking of not doing it and documenting the same by saying that the "Booking Feature(button) can be used for 'Booking', 'Unbooking' (by setting 'Customer' to blank), Rebooking (by setting the 'Customer' to a different value) a room.".
Do you think this is reasonable?
author and jackaroo