Since you're asking about the need, let me bring you an example: (images and documents are both just files so we can discuss storing files in the database not just images)
I have a bunch of documents that my customer can upload through the admin interface. He can then assign read permissions to the documents. The problem with files lying around on the disk is that it's hard to forbid access to them once people know the URL to them. I could use UNIX permissions to solve this and write a view that returns file data, but then we'd be back to the same overhead problem you were mentioning. Erik On 08.09.2008, at 15:06, Ludwig wrote: > Is there a pressing need to do this? > > I think the design decision here was that serving image files to > users is something that web-servers will be able to do with much > less overhead. > If you need to perform image manipulation on the fly, maybe have a > look at sorl.thumbnail (http://code.google.com/p/sorl-thumbnail/), > which gives you a lot of the power of the Python Imaging Library > within a template tag, while leaving your image data on the file- > system. > > Ludwig > > 2008/9/8 nsash <[EMAIL PROTECTED]> > > How can I upload an image in the database? As it is now , in database > is saved only the path to it. > The image itself is in the file system. > > Thanks > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
