Win a copy of AWS Security this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

bookedflights.db maybe?

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.
Posts: 17346
Mac IntelliJ IDE 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.
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic