• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

bookedflights.db maybe?

 
Steve Marks
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it a good idea to save the information from a booked flight into a different database, such as bookedflights.db? keeping similar fields to db.db
but changing the available seats to seats booked and creating a client id as the key.
I know it does not say anything about this in the spec, but in any real world app it would be a must.
Could someone tell me if I am just making work for myself, or it is a good idea?
I would rather not do it as it presents more problems than benefits.
If I do not create a new database I cannot see the point of passing a reference of the client to the bookSeats method, as it works fine without.
Any suggestions would be welcome.
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Nah, you don't need to save any information on flights that someone has booked. However, you do ned to decrease the number of available seats in the db.db file everytime someone books seats.
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic