hi all, i have a scenario that require me to design a database for badminton club reservation purposes, so far,
i have come with the following entity/table,

->Customer
->Court
->ReservationRecord
->Player
->Package

Any other suggestion for this scenario?

what's a package?

and what's the difference between a player and a customer?

hi
A customer can place reservation,
well inside the reservation, we may have our friends joining the game too,
thats why i propose a player table here, to record players information into the database(numbers of player,player name,gender, and under which reservation number), a player information may repeated when he/she involve in other new reservation~