#19126: runserver versus model validation
-------------------------------------+-------------------------------------
Reporter: direvus | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: 1.3
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by direvus@…):
Replying to [comment:6 aaugustin]:
> That would make it trivial to disable model validation when needed.
That seems like a good idea, but it wouldn't really solve the problem I
originally posted about. I can already disable model validation, but I'd
rather not. What I want is for model validation to run, and report its
findings, but not to prevent runserver from starting up.
Model validation is great! I want it to do its thing. The issue is that
runserver's response to any model validation problem at all, is to commit
immediate suicide. If all model validation problems were of a fatal
nature, that would make sense. But they're not, so it doesn't.
--
Ticket URL: <https://code.djangoproject.com/ticket/19126#comment:7>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
