Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: customer id

 
steven Gu
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have another question about customer id:
in the database i received. a column named "owner" .
sun said it's
<for this application, you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them. If this field is all blanks, the record is available for sale.>
I didn't get the real meaning.
when i booking a record, i must update the owner ?
But if update, the record will not booked , because the field is not blanks,
even the field of <Maximum occupancy of this room> is > 0?
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12012
216
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Steven,
Thanks for fixing your name.

when i booking a record, i must update the owner ?

Correct - you must store the number that the user types into the owner field of the database.

But if update, the record will not booked , because the field is not blanks,
even the field of <Maximum occupancy of this room> is > 0?[/QB]

The "Maximum occupancy" is a read only field - you never need to change it. It is something that the user of your software will be able to look at to determine whether the room will suit the people who want to book it (if a husband and wife wish to book a room, they may not be too happy if they have to have separate rooms (or maybe they will )).
If the owner field consists of all blanks then you may book the room.
Once you have booked the room, the owner field will no longer consist of all blanks so no-one else may book the room.
Regards, Andrew
 
steven Gu
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot first
Now I get your meanings:
When somebody want to book a room , he only do:
input the 8 lengths Id in the <customer> Column of Client's JTable .
Then in database the column of <customer> will be store the Id of user
input.
So this also means this record can not be booked by another people.
Am i right?
Thanks again!
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12012
216
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Steven,
Yes - you've got it.
input the 8 lengths Id in the <customer> Column of Client's JTable .

By the way - it is up to you whether you have a modifiable table, or whether you have a popup dialog box, or whether you have a separate screen to enter the booking information. There is nothing wrong with having a modifiable table and having the user enter the data that way - it is entirely up to you.

Regards, Andrew
[ February 05, 2004: Message edited by: Andrew Monkhouse ]
 
steven Gu
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Best Regards, Andrew!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic