On 7/30/07, David Cramer <[EMAIL PROTECTED]> wrote: > In my opinion BlobField's need some kind of support inside of Django > before the coming of 0.97 release. > > They have never been officially supported, but they were at least > usable (as say a TextField) before Unicode. Now they're unusable as > you run into encoding/decoding issues.
Hey David, In order to add BlobField support to Django, you'd need to answer at least a few questions -- * How is it represented in the admin interface, if at all? * How is it represented as a form field, via form_for_model()? * Are the entire contents of the blob retrieved along with the rest of the fields, each time the object is selected from the database, or is it lazily loaded somehow? * Is the interface for adding/changing blob data any different than adding/changing other field values? There are two reasons blobs haven't been implemented in Django. One, it's the personal opinion of the developers (or, me, at least, and I'm pretty sure about Jacob and Simon) that a database shouldn't be used to store binary data. Two, the above questions, plus the ones that I inevitably forgot to include in the list, have not been answered, making the whole issue a non-starter. If you can answer the above questions and come up with a patch that doesn't involve hacking too much of Django's innards, I would be willing to look at it. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
