The only alteration I'd consider is instead of keeping image ID 1,2,3 etc for each user and storing the image name (or path or whatever that is) in the table, make imageid a fk to an images table and store the image name there. This way people can use the same image without duplication in this table and the whole thing is normalised. Keep the composite key in this table and all is well.
On 7/5/05, Michael Dinowitz <[EMAIL PROTECTED]> wrote: > I'm building out a new photo gallery and I'm looking at different DB designs. > The gallery will have pictures on a per person basis as well as a per event > basis. [snip] -- Geeque - accept the geek within and get your friends off your back - http://www.cafepress.com/geeque/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase RoboHelp from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=59 Message: http://www.houseoffusion.com/lists.cfm/link=i:6:2315 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/6 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:6 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
