The problem with keeping the price with the album. What if the album goes on sale? You'd change the price in the album table then suddenly anyone who bought the album previously shows that they paid the sale price. You would at least need to add a history table or make sure that the sales table shows the actual price and isn't just hooked to the album table. It's been a long day- hope this is coherent enough.
-----Original Message----- From: Douglas Brown [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 5:01 PM To: CF-Talk Subject: SQL? I am trying to figure out how I should set up a database for an ecommerce site. I will be selling music CD's. Each artist can have several albums, and each album can have several tracks. I am pretty sure I will need 3 tables for that info. What I am wondering , is where should I keep pricing info and such? Should it be in the album table or should there be a seperate table for pricing etc. Any insight would be helpful There are two major products that come out of Berkeley: LSD and [Unix] BSD. We don't believe this to be a coincidence. Doug Brown ______________________________________________________________________ Why Share? Dedicated Win 2000 Server · PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
