SCJP 1.4<br />SCJD 1.4 (in progress)
"The UrlyBird catches the certificate. And he's gonna FlyByNight"<br /> <br />SCJP 1.2/5.0, SCJD, SCBCD, SCWCD, SCEA
Originally posted by Wei-ju Wu:
From the user perspective it would be even better if the records that can not be booked are not be displayed at all, at least so I would think.
In Data: before the update is called this will be checked. But this has also one drawback:
the user will not be notified that the booking is not complited.
"The UrlyBird catches the certificate. And he's gonna FlyByNight"<br /> <br />SCJP 1.2/5.0, SCJD, SCBCD, SCWCD, SCEA
Originally posted by Wei-ju Wu:
Yes, it is the other thing I added to my business logic, it is checked during search and booking so you can neither find nor book records that are already booked by some other person.
I understand that one could discuss about whether to diplay or not to display the records that are not available anyways, from my point of view I would not be interested in hundreds of records that could not be booked .....
Originally posted by Ta Ri Ki Sun:
Redundant code?
Originally posted by Ta Ri Ki Sun:
I'm with you, but surely the system is not built only for booking. A user may only be interested to know which rooms/dates have in fact been booked, or by which client, perhaps even tracking a client's stay at various hotels over a certain period, and your GUI will never show them that.
Besides the system has search functionality, so the users can narrow their results.
Also consider that cancellation of a booking, if implemented in future, would require more coding effort than it would otherwise need.
"The UrlyBird catches the certificate. And he's gonna FlyByNight"<br /> <br />SCJP 1.2/5.0, SCJD, SCBCD, SCWCD, SCEA
SCJP 1.4<br />SCJD 1.4 (in progress)
Consider Paul's rocket mass heater. |