#5361: Support pluggable backends for FileField
------------------------------------------------------------+---------------
Reporter: Marty Alchin <[EMAIL PROTECTED]> | Owner:
Gulopine
Status: new | Milestone:
1.0 beta
Component: Database wrapper | Version:
SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 1 |
------------------------------------------------------------+---------------
Comment (by david):
Re save(): I agree that a _save() function is more interesting given the
complexity of the actual save(). For the moment, I've only copied tests
which looks interesting to me but I'm open to a more complete storage
specific test suite.
Re path(): to me url == path for a remote storage and that's what I've
done (there was some troubles if path() is not defined for a storage with
the previous patch but I can't remember why). I define path() function
because I'd like to keep the order of !FileSystemBackend but it is copied
in url() a couple of lines below.
--
Ticket URL: <http://code.djangoproject.com/ticket/5361#comment:74>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
