On 9/17/07, Marty Alchin <[EMAIL PROTECTED]> wrote: > 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
While it's true those are three separate issues, it makes more sense to me to solve 'em all in one fell swoop. Something like #5361 has been on my radar for quite some time now (file storage right now is something of a pain in a large system), so I can merge my code with what you've already written and get a lot of cool shit done. > 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. Yeah - once I check the file storage code in, I'll look over the tickets marked as dups and reopen any that aren't, really. > 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? In general, more backends is better, of course :) I'd be +1 on just including all of 'em (though SVN is a bit marginal), but if others feel differently I'd love to hear about it. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
