On 9/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 9/16/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > * Lots of things related to FileField which would be fixed by the
> > pluggable backends proposal.
>
> s/would/will/ -- I'm gonna try to have this wrapped up in the next couple 
> days.
>
> Jacob

Malcolm pointed out during the sprint that my patch for #5361 is a bit
over-reaching, as it technically tackles three separate problems:

 * A new API for access to files associated with models
 * Moving file saving into FileField and ImageField for easier subclassing
 * Moving to pluggable file storage and including a default backend

I haven't had a chance to do so, but if it makes more sense, I can
split those into three separate tickets. It'd make them a bit harder
to merge together, since each would have to be written in a way that
wouldn't require the other two, but it's certainly possible.

Also, I'm not sure #5361 will actually solve many of the FileField
problems currently in use. For instance, James marked #3588 as a
duplicate of #5361, even though nothing I've proposed would have any
impact on the size of the database field used for storing file
information. Sure, certain backends might store less information in
that field, but it won't do anything for the standard storage
mechanism.

Also, if/when this filestorage stuff gets committed, what backends do
we want to provide batteries-included? The patch I have so far just
includes a filesystem backend, but I've worked out could-be-working
backends for S3, WebDAV, MogileFS and I'm almost done with one for
SVN. I wrote them just as tests to see if the backend protocol was
sufficient for the various options, but should they (or at least some
of them) be included in core as well?

-Gul

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

Reply via email to