Re: images in database... a suggestion
Re: images in database... a suggestion
- Subject: Re: images in database... a suggestion
- From: Georg Tuparev <email@hidden>
- Date: Mon, 12 Dec 2005 10:43:23 +0100
| I can confirm Geoff's words in principle. But there is a caveat. If you put more than, say, 2k files in a folder, the file systems slows down. We have a framework that deals with this problem by spreading files in auto-generated folders. Also it is always a good idea to store images (or other BLOBS) in a separate DB (schema) and if the DB supports, use a raw device instead of file system...
just my €0.02
gt On Dec 12, 2005, at 9:31 AM, Geoff Hopson wrote: This is exactly how I did the Fortnum & Mason site - they had an extensive product catalog whose images were stored in a database. when the catalog was ready to go live, the images were exported to the file system under the web server. The web app had a runtime switch (mode = deploy) for the 'production' apps which I could use in a WOConditional (set a boolean in Application, then test on application.deploy in the WOConditional. Developers didn't set the switch and therefore would read images from the database.
Worked well.
Georg Tuparev Tuparev Technologies Klipper 13 1186 VR Amstelveen The Netherlands Mobile: +31-6-55798196 |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden