Hey guys. I'm used to building databases that don't change too frequently and have structures that are pretty common. For eg a music database; which would have multiple tables for categories like artists, tracks, albums etc. and your php would bring the necessary information together.
But I want to build a restaurant reservation system for a school project and while scoping out the idea and functionality and what not I got to the stage where I need to sketch out my database structure.
I realize this will be quite different in the sense that the database will be very active and dynamic, changing constantly on the fly with reservations being made, changed, and tables being added, moved, changed etc.
So I'm wondering what sort of structure will my database need? Would I break it down like any other database and have a customer table, a tables table, a reservation table etc. Or would you just create a reservation table that would have all the necessary fields such as date, name, time, table, party size, notes etc
thanks!