Toys 4 U is a company that specialises in toy hire for parties, kindergartens and play groups. They
also offer equipment for infants and babies for hire. Toys 4 U can own several copies (TOYCOPY) of
each toy (TOY). For example, a store may have 10 copies of the toy Rocking Horse. In the database,
Rocking Horse would be one TOY, and each copy would be a TOYCOPY. A hire transaction (HIRE)
involves one or more copies being hired to a member (MEMBERSHIP). A copy can be hired many
times over its lifetime; therefore, there is an M:N relationship between HIRE and TOYCOPY.
DETAILHIRE is the bridge table to resolve this relationship.
Requirements
1. Design your ER Diagram with all entity names, attribute names, primary and foreign keys,
relationships, cardinality and participation indicated. You may add entities or attributes as you
see fit. You will need to normalise all of your entities, to resolve any many to many relationships.
? Your attribute names, primary and foreign keys should be indicated as per the conventions
given in the lecture slides (i.e. entity/table names in capitals, attributes as proper nouns,
primary key underlined and foreign keys in italics).
? All many to many relationships should be resolved, and you should include a discussion of
normalisation including the normal form that each entity is in and why that is optimal. Also, a
discussion of how normalisation was achieved for that entity.
2. For each entity, create some example data for that entity. Include 5 rows of data for each entity.
3. Write the SQL code to create the table structures from your developed ERD. The structures
should contain the attributes specified in your ERD. Use data types that are appropriate for the
data that will need to be stored in each attribute. Enforce primary key and foreign key constraints
as indicated by your ERD.
4. Write the SQL code to insert your data from (2) into the SQL table structures