Joel,
many-to-many relationship as you wanted to do.
Wednesday, August 20, 2003, 4:48:21 PM, you wrote:
Joel> Everyone:
Joel> If this has been asked to death, I apologize now. : )
Joel> I'm currently redoing a system, and the way the previous developer
Joel> was storing data for a user was to have a list of ID's as a list in 1
Joel> column of a table. Like so:
Joel> Members table:
Joel> 1|Test|[EMAIL PROTECTED]|1,2,3
Joel> 2|Test|[EMAIL PROTECTED]|3
Joel> 1|Test|[EMAIL PROTECTED]|1,3
Joel> etc
Joel> Songs table:
Joel> 1|Song Name
Joel> 2|Song #2
Joel> 3|Song #3
Joel> etc
Joel> Now, after reading some stuff here, I don't think this is the best way
Joel> to do it. So, from a dbms standpoint, what is the best practice for
Joel> storing this data? A seperate table with just the members ID and 1
Joel> song ID? Or is there a better way to do it.
Joel> Note: This is a MySQL db, and not MS SQL or Oracle. So I can't do
Joel> sub-queries or SP's.
Joel> Thanks for your time.
Joel> ======================
Joel> Joel Firestone - Developer
Joel> http://www.dmv.com/
Joel>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/lists.cfm?link=t:6
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:6
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=<:emailid:>.<:userid:>.<:listid:>
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
http://www.cfhosting.com
