> is your idea to have the image paths stored in a diff table then > the rest of the product info?
If you're relating multiple images to products, and you're using a relational database, storing images in a different table would be the way to go. > and then ur uploading the images and making a new record for each > picture and using the productID to pull them together with the record when > its shown? Exactly. > i really dont get how thats more elegant, seems more chances for it to > break in a few more places It's more elegant in that it solves the problem through a scalable, relational solution rather than a brute force, static, non-relational manner. It can be altered, added to, or removed without going back to square one. > see joe what i was doing was trying to take the looping out so that > there is only 1 insert and the images are stored in the same table > as the rest, so that way i can call them as i want without > having to pull outta extra tables. Then why are we using relational databases? -- For Tabs, Trees, and more, use the jComponents: http://clearsoftware.net/client/jComponents.cfm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190202 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
