On Mon, Jul 14, 2008 at 11:02 AM, Rudolph <[EMAIL PROTECTED]> wrote:
> Ticket 5361 provides a way to accomplish this by writing a custom
> backend:
> http://code.djangoproject.com/ticket/5361
>
> The ticket is on the "maybe" list for 1.0!

I was afraid someone would bring up that ticket on this thread. That
ticket has nothing to do with storing files in a BLOB field, but
instead, its backends allow you to swap out different file systems,
such as MogileFS or even Amazon's S3. A BLOB isn't really a file
system at all, it's just designed to store a single field, so calling
things like blob_backend.save(filename, content) make absolutely no
sense.

That said, I will concede that some of the incidental changes that
#5361 introduces *could* make it a little bit easier to write a BLOB
field. It organizes FileField a bit better, so it might be easier to
subclass it when making the custom field. It would be an interesting
test to see if those changes help in more cases than just those I
expected.

There's still a fair amount of work to be done between now and having
a working BLOB field, and some of the changes in #5361 might make that
slightly easier. The rest of it, including the pluggable backend
support, will just add completely useless overhead and cause more
confusion than it will solve problems.

There's already a ticket[1] for adding a BLOB field to Django, which I
haven't been following. If it gains traction, I'd be willing to invest
some energy in helping it along. For the moment, I'll just settle for
asking people not to put too much hope in #5361 solving this
particular issue.

-Gul

[1] http://code.djangoproject.com/ticket/2417

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

Reply via email to