In this Lesson
You will be introduced to the data model used by Party Pool solution.
Database design is beyond the scope of these lessons so we have simply provided a design. The data model is more simplistic than what would exist for a ‘real’ solution and yet it models the types of relationships you will find in any robust solution that you would create.
The data model you will be using consists of 5 tables. The definitions for these tables are contained in the tables folder of your Party project.
The party table is in the demo database and it contains the summary information for a party.
Food Catalog Table
The food catalog table is in the demo database and it contains the inventory off all the types of food that can be provided for a party.
The menu table is in the demo database and it contains a list of the food items ordered for a specific party.
The guest table is in the demo database and it contains a list of the guests invited to a specific party.
Party Theme Table
The party theme table contains the theme that is being used for a specific party.
The ability to capture a party theme is the ‘enhancement’ that the acme party planners company has asked to be added to the system.
This is the enhancement that we do not want to add to the core product. In a real world this piece of information is something that you probably would want to be part of the core product. But, this is simply used in an exercise to make a point – even while not making practical sense.[ work with me people! you will like the exercise that uses this bit of information ]
So, unlike the other tables, this table is in the acme database.
We will talk more about the specific use case for this data element in one of the last lessons.