13 messages in com.mysql.lists.mysqlRe: Mysql database design assistance,...
FromSent OnAttachments
Gerry Chu04 Dec 2000 20:40 
Gerry Chu04 Dec 2000 21:01 
Jack Dempsey04 Dec 2000 21:08 
Gerry Chu04 Dec 2000 21:28 
Steve Lewis04 Dec 2000 22:58 
Gerry Chu04 Dec 2000 23:02 
TSHACK04 Dec 2000 23:29 
Gerry Chu05 Dec 2000 00:28 
Bob Hall05 Dec 2000 04:38 
Carsten Gehling05 Dec 2000 04:40 
Carsten Gehling05 Dec 2000 08:37 
Steve Lewis05 Dec 2000 17:15 
Gerry Chu07 Dec 2000 21:34 
Subject:Re: Mysql database design assistance, please?
From:Carsten Gehling (cars@sarum.dk)
Date:12/05/2000 08:37:50 AM
List:com.mysql.lists.mysql

From: "TSHACK" <TSH@SILVER-BAYOU.COM> Sent: Tuesday, December 05, 2000 4:57 PM

The redundancies marked with * are only a problem because MySql doesn't support referential integrity (and thereby cascading updates) between relations (I suppose that Name and Events contains the actual text and not just an identifier).

Competition is redundant because I assume the same competition could occur several years, correct?

Ah, I didn't get it that an Event would be a subset of a competition.

Not really a subset. Rather an extra layer of specification. If Event was a subset of Competition, you would have to define every Event once for each instance of competition. On the other hand, that would give you the opportunity to specify different events for each Competition, which you cannot do in the structure that I made.

- Carsten