Read the idea
Open the reading →A waterfront rental business records customers, kayaks and bookings. A customer has a name, an email and an optional phone number. A booking belongs to one customer and has a booking date.
An entity has facts of its own. An attribute describes an entity. Split a composite name if the business needs its parts. Put multiple values or repeated events in their own records. Keep a derived amount calculable from its inputs.
Use a surrogate id as the primary key when following the course convention. Keep a required natural identifier such as a unique email NOT NULL UNIQUE when the requirements establish that rule.
Worked example
Entities: customer, kayak, booking. The list of kayaks represents multiple related facts and belongs in booking_items, one row per booked kayak.
Your task
Identify three entities, give two attributes for each, and explain why a list of rented kayaks should not be stored in one booking column.
Give me a hint
Use the question’s requirements as your checklist. State an assumption if the wording does not establish a rule.
Compare with a worked answer
Entities: customer, kayak, booking. The list of kayaks represents multiple related facts and belongs in booking_items, one row per booked kayak.
Using an answer is useful practice. Record what you learned; it does not demonstrate independent mastery.