Forum: Database Design Apr 19th, 2009 |
| Replies: 5 Views: 591 You need a Supply ID primary key in the Supply table with event no and wedding no as foreign keys. The way you have it set up currently, each event/wedding can have only one supply (I'm assuming the... |
Forum: Database Design Nov 12th, 2008 |
| Replies: 17 Views: 3,079 What is the difference between the lecture entity and the session entity; isn't a lecture just a type of session? Same with practical session and session.
I see you removed the relationship... |
Forum: Database Design Oct 30th, 2008 |
| Replies: 8 Views: 1,097 This is how I would approach the issue. I would have one table to track the bills, one table to track the people and one table to track the transactions:
Bills (ID, amount, date billed, date due,... |
Forum: Database Design Sep 22nd, 2008 |
| Replies: 2 Views: 1,663 This is my recommendation:
Create one 'user' table that stores, at a minimum, UserId, but could also store name, DOB, etc.
Create one 'Attributes' table that stores all the different... |