VCE Stuff > VCE Computing: Data Analytics

hgk

(1/1)

bard_4116:
h

Lasercookie:
The way you listed all the data required looks pretty well split into tables and all that already
--- Quote ---movies, session details, booking made and patron details
--- End quote ---
could very well be our 4 tables.

The movies table will contain the title and synopsis.
The session details will contain the movie, date and time. The movie here will be related to the movies table, so that we can get the data like the movie title etc.
The patron details will have the name and contact number.
The booking made will presumably contain details about what session has been booked, how much it cost (perhaps) and who made the booking. So you have the session here related to the session details table (so that you can retrieve the date, time etc.), and also related to the patron details table (so that you can retrieve data about name of the person etc.)

And of course you'd have primary keys and what not for each table. The good thing with having database relationships is that you can contain all the specific data in one table (e.g. the movie title and synopsis), and then in another table (say session details), all you need to use is the movie id that you've assigned - rather than duplicating all the other data.

You'll want to think about what kind of relationships they'll be too. Will they be one to one, or one to many, or many to many etc.? You can reason this out by wording out what you want e.g. many customers will attend one session, one movie is shown at one session, one customer will make one booking (you could also extend the database to allow more than 1 ticket to be bought, and then the different ticket prices too) etc.

Navigation

[0] Message Index