#19126: Allow runserver to bypass model validation
-------------------------------------+-------------------------------------
     Reporter:  Brendan Jurd         |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Core (Management     |                  Version:  master
  commands)                          |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Brendan Jurd):

 Replying to [comment:12 boxed]:
 > This ticket was never fixed. The SILENCED_SYSTEM_CHECKS feature doesn't
 do what you would think it does based on this discussion, and even if it
 did work as the documentation says (it doesn't!) it would still be no
 good:

 Wow, OP here.  thanks for the reply, boxed.  I certainly was surprised to
 see this old thing pop up in my inbox.

 I agree with your assessment that the original request was never
 satisfied, and that this ticket was closed improperly.  I didn't get too
 worked up about that at the time, because I'd already found a way to work
 around the particular issue I was having.

 I think my original point here is still valid, I still believe that
 runserver should proceed to run even if model validation fails, or at
 least, there should be an option to enable that behaviour.

 Having said that, in the eight years (yikes) since I wrote the original
 ticket, I've long since stopped trying to coerce the Django ORM into doing
 anything beyond the basics.  These days I just bomb straight out to raw
 SQL for anything even slightly exotic.  There's a lot to like about
 Django, but its ORM (really, ORMs in general) is just a big old energy
 drain for me.  It took me a while to realise this.  SQL is fine.  It was
 fine all along.

 So TL;DR: you're right, but I am no longer invested.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19126#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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.46b2398be5c21ef4391d5900e16c5a2f%40djangoproject.com.

Reply via email to