You have a friend that runs a motor bike club that holds racing events at various venues on weekends, on a monthly basis. Some venues are private race tracks and some are dirt tracks on private farms (ie. none of the racing is done on public roads). Racers must provide their own bike and appropriate safety gear. Each racer must make their own way to each of the racing events venues. Each time a competition day is scheduled, a number of members register for it. When they register they specify the events they wish to compete in. Currently the club manually keeps records of
- Each member and their details
- The days that have been scheduled to hold races and the venue (location) of the race day.
- The individual races that will be held on the particular race day (eg: start time, length etc)
- The members that have registered for each race they wish to compete in.
- The results of each race are recorded (ie each competitor's time for the race and also who won, came second etc). The club wish to computerise their records. What you have been asked to do is provide the database model for the system.
Pass/Credit Level - Design
To assist your friend, try and come up with a small database design for a new system. Provide the following:
- Entity Relationship Diagram.
- Relational Model (showing fields, primary keys, foreign keys and concatenated keys).
- Justify the choices you have made. Are the entities and relationships you have chosen free of problems? What assumptions have you made?
Higher Level - Construct and Test
- Create the database tables using SQL statements in your own database. Include
- CREATE TABLE queries - that create each of the tables in your design
- INSERT INTO queries - that insert values into your tables (at least 5 rows per table) Write some queries to test out the database.
- One query should be a simple one involving one table and selection criteria.
- The second query should involve a join (at least 2 tables)
- The third should be a group by query.
- Fourth query that involves a nested query.