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 -~----------~----~----~----~------~----~------~--~---
