Depends on if you need it. It sure sounds like a multi server environment. IMHO storing images in a database is still less pain than NFS or similar. Looking into Amazon S3 might also provide you with a suitable solution.
If it has to be local (something you control), check out an alternative database. I'd recommend something like CouchDB. It allows you to attach images to a document and it can even serve them directly via HTTP. :) Till 2009/5/14 Michael Tramontano <[email protected]>: > Probably important to note this would be mySQL, and most likely innoDB > (though I believe the engine can be on a per-table basis) on linux ;) > > > > -mike > > > > From: Michael Tramontano [mailto:[email protected]] > Sent: Thursday, May 14, 2009 2:07 PM > > To: [email protected] > Subject: [fw-general] Storing images in the database > > > > What are you general feelings about actually serializing images and storing > them in a database vs. storing just the path ? > > > > -mike
