#4431: manage.py loaddata should have better error reporting
-------------------------------------------+--------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Component: Tools
Version: SVN | Resolution:
Keywords: manage.py loaddata dumpdata | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------------+--------------------------------
Changes (by Jonathan Ballet <[EMAIL PROTECTED]>):
* keywords: manage.py loaddata => manage.py loaddata dumpdata
Comment:
The same problem occured when using {{{dumpdata}}}, if the database is
inconsistent (differences between the models and the schema).
For example, consider a class A with a FK to class B. If the FK is removed
from the database, and rows in table_A refers to id which are not in
table_B, {{{dumpdata}}} will fail with a "{{{B matching query does not
exist.}}}"
This is ''not'' a bug in {{{dumpdata}}}, but if it reported errors more
accurately, it might be easier to debug.
--
Ticket URL: <http://code.djangoproject.com/ticket/4431#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
