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.