#8466: FileField path url dumpdata/loaddata issue
------------------------------------+---------------------------------------
Reporter: Ian Ward | Owner: nobody
Status: new | Milestone: 1.0
Component: Serialization | Version: SVN
Resolution: | Keywords: FileField path url
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by Ian Ward):
* needs_better_patch: => 0
* component: File uploads/storage => Serialization
* needs_tests: => 0
* summary: FileField.size triggering SuspiciousOperation exception =>
FileField path url dumpdata/loaddata issue
* keywords: FileField size => FileField path url
* needs_docs: => 0
Comment:
Now, this looks like an export issue. I dumped the models into an XML
file from a Postgres database where the file paths looked like:
YEAR/MONTH/NAME. The XML file contains "/media/uploaded/YEAR/MONTH/NAME"
and when importing to sqlite the database contains
"/media/uploaded/YEAR/MONTH/NAME", causing the problem above.
new instances of the model *do not* contain /media/uploaded/ in the
database, it just looked that way from the admin site.
--
Ticket URL: <http://code.djangoproject.com/ticket/8466#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
