[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: Digital Jukebox
- To: ukha_d@xxxxxxx
- Subject: RE: Digital Jukebox
- From: andy.powell@xxxxxxx
- Date: Fri, 16 Mar 2001 13:35:40 +0100
- Delivered-to: rich@xxxxxxx
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
Mark,
What if an artist leaves a band but does a song with them later?
A.
"Kaye, Mark" <mark.kaye@xxxxxxx>
16/03/2001 11:30
Please respond to ukha_d
To: "'ukha_d@xxxxxxx'" <ukha_d@xxxxxxx>
cc: "Mylod, Colum" <colum.mylod@xxxxxxx>
Subject: RE: [ukha_d] Digital Jukebox
Just having a quick bash at the schema for a comprehensive
Artist/Band/Album/Song database. I have worked out the fairly complex
relationship between Artists, Bands and Artist membership of bands. Can
anyone see a flaw in the following schema (additional columns in each
table could easily be created, I'm more interested in relational problems
with the schema):
Artist Table Table which holds individual Artist info
artistid ID of Artist
fname First Name of Artist
mname Middle Initial/s or Middle Name/s
lname Last Name of Artist
dob Date of Birth of Artist
height Height of Artist
Band Table Table which holds band details
bandid ID of Band
bandname Name of Band
estdate Date of Establishment
cesdate Cessation Date
Member Table Table which manages the relationship between bands and
artists
artistid ID of Artist
bandid ID of Band
startdate Date Artist started in band
enddate Date Artist stopped in band
This schema should allow for individual band/artists (one man bands!) and
also multiple bands with single or multiple artists. Can anyone see any
major flaws here?
Cheers,
M
Home |
Main Index |
Thread Index
|