I wouldn't save to a DB. Just move the file based upon the user id or something and automatically create folders based on the user id or whatever.
I would think it to be a security hazard if you did do that. Also, you will increase the size of your db which could degrade performance. People are generally very liberal in their use of "findAll()" in Cake. Loading ALL...... the image data would be quite interesting if you had many images. Whether you display those images or not, just parsing all that to an array...mmm...so you gotta be careful how you handle data. NOT that it's impossible to store the images in a DB table and not that it can't be effective to do so. It could also tidy up a bunch of directory structures all over the site and calling back those images could perhaps be very easy, rather than messing with DS this and DS that yada yada and if it's installed to a different path on another server...you get the idea. There's two sides to the coin. I have a fairly simple file upload component that I've put together, it's really just snippets of various parts of other file upload scripts found on the wiki and cakeforge. I will ultimately try to post it as a tutorial soon. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
