#10200: loaddata command does not raise CommandError on errors
-------------------------------------+-------------------------------------
Reporter: lgs | Owner: nobody
Type: Bug | Status: reopened
Component: Core (Management | Version: SVN
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: exit status | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by yishaibeeri):
* status: closed => reopened
* cc: yishaibeeri (added)
* component: Core (Serialization) => Core (Management commands)
* version: 1.0 => SVN
* keywords: => exit status
* resolution: duplicate =>
* stage: Design decision needed => Accepted
Comment:
Reopening, as the fix for #16026 did not, eventually, fix this issue. In
trunk (as of rev 17029) the exit status of a failed loaddata invocation
(e.g., bad value in a fixture causing a DatabaseError) is still 0.
--
Ticket URL: <https://code.djangoproject.com/ticket/10200#comment:11>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
