#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: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
Any news about this ?
I've just hit this. We have a buildbot and when the loaddata fails, we
cannot easily detect it. So, having run "set -e" in my bash doesn't help
in this case, and then tests are run. The tests fail and the error was
that loaddata failed, very hidden in the output.
If the exit code of the command could be just like any standard unix
command (!=0 on error), that will be great and made life for sysadmins
like me happier :)
Btw, we are using django 1.3.1 in case it matters
--
Ticket URL: <https://code.djangoproject.com/ticket/10200#comment:13>
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.
