I have been influenced by the argument given a sites such as http://cakebaker.42dh.com/2006/04/15/file-upload-with-cakephp/. There is a logic to me, that having the image and the data surrounding the image are in one place, not devided between two places which would require attention to not allowing the two from becoming out of sync.
I am certainly open to opposing views as I am new to dealing with large quantities of images. On Jun 6, 1:43 pm, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On 6/6/07, peterhf <[EMAIL PROTECTED]> wrote: > > > > > I am developing a community site in which members can upload photos of > > themselves for display on their page. My plan is to store the image > > files in a database. When a photo is need for display, it is retrieved > > from the database and stored in a directory in the Cake directory > > structure. It can them be displayed on the page using "$html- > > >image()". > > Why bother with the middle step of retrieving from the database and > storing in a directory? If you write the file to the filesystem as > soon as you've uploaded and verified that it's a valid image, you can > cache it for display using a variety of methods (Cake and non-Cake). > > I've never understood why people would store images in a database > rather than the file system. Is there an advantage to this? > > -- > Chris Hartjes > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark -http://www.littlehart.net/attheballpark > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
