#10790: Too many joins in a comparison for NULL.
-------------------------------------+-------------------------------------
Reporter: mtredinnick | Owner: akaariai
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
Unfortunately the patch does have too much going on for one patch. I could
rewrite it to smaller pieces, but I am not sure if the effort-reward ratio
is there.
The changes aren't _that_ big. The patch changes around 250 lines of
django core code, and a large part of those changes are reindent of the
model._meta traversal code.
The tests did pass and I have a confident feeling that the patch is doing
the right thing. However I am not going to push this forward today. I have
been doing too many mistakes lately (#13781 did need a few tries, and I
just did the equivalent of DELETE * FROM tbl in a production DB...). So, I
will do something completely else for a couple of days and then revisit
this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:48>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
