| bio | website | |
|---|---|---|
| location | Budapest, Hungary | |
| age | 27 | |
| visits | member for | 1 year, 7 months |
| seen | May 2 at 20:35 | |
| stats | profile views | 7 |
|
Oct 6 |
comment |
Representing N:N relation as a functional dependency in a database design If I were to implement this in a real-world system I would use surrogate keys and a third table with two foreign key columns. I'm going to ask him on Monday about this and accept your answer if there really is no solution. |
|
Oct 6 |
awarded | Supporter |
|
Oct 6 |
comment |
Representing N:N relation as a functional dependency in a database design I think you're right but my teacher is a natural key zealot and he wouldn't accept any other solution. |
|
Oct 6 |
comment |
Representing N:N relation as a functional dependency in a database design Category is a primary attribute in your example, which must be unique. |
|
Oct 6 |
revised |
Representing N:N relation as a functional dependency in a database design deleted 2 characters in body |
|
Oct 6 |
awarded | Editor |
|
Oct 6 |
revised |
Representing N:N relation as a functional dependency in a database design Changed title |
|
Oct 6 |
awarded | Student |
|
Oct 6 |
asked | Representing N:N relation as a functional dependency in a database design |