Thanks Oliver, hadn't researched that yet I have decided to use lighttpd to serve up the images now, looks to be much more reliable.
On Jul 14, 11:48 am, Oliver Andrich <[EMAIL PROTECTED]> wrote: > Hi Luke, > > I have tried this in an asset management system I am currently > implementing for my company, which is ment to store a lots of images > (round about 300.000+). Generally it is a very bad idea, at least this > is what I have found. I ignored this article > > http://mysqldump.azundris.com/archives/36-Serving-Images-From-A-Datab... > > at first, but after some serious testing I have to admit, that > everything is true what the author says. > > So, if you plan to store some images in your database, it might be > okay, but if you plan to serve a lot of images it is not. You are > better of with storing images in your filesystem and serving them from > a seperate http server. > > Hopefully, I haven't told you something you already know and have > already considered. > > Best regards, > Oliver > > Am 14.07.2008 um 16:41 schrieb lukeqsee: > > > > > I know you can store images in a BLOB field in mysql, but is it > > possible with Django models? > > > Thanks, > > Luke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
