> So you're saying like this...?
>
> Albums
> ------
> ID,Artist,Title,Label
>
> Tracks
> ------
> Title,Length,TrackNumber,AlbumID
>
> Where there is one album table and one track table, and each
> track references back to the album that it is a member of?
> I'm liking that... It doesn't make it easy to dig through the
> database by hand, but in all likelihood, nobody will ever
> need to do that.
>
> Anybody think this is bad?
No. It is, as far as I and several books on database design are
concerned,
one of the very few good ways to represent that particular set of data.
Normalisation (get a book about database design, google around, etc -
but
learn about it.) is generally good. (Not always though.)
-S
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
