#20002: Model inheritance depth may result in invalid SQL queries
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: nobody
<django@…> | Status: new
Type: Bug | Version: 1.5
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Keryn Knight <django@…>):
* needs_docs: => 0
* version: 1.4 => 1.5
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
I've since tested this on 1.5 and 1.6 (master at
477d737e1e6bdf93950c8a381906925c594fac2f)
* It still occurs in 1.5 (so I've bumped the version affected to reflect
this)
* It is fixed in 1.6
Looking around Trac, I'd guess tickets #16572 and #13781 were probably
where the underlying problem got fixed.
I'm not sure if there are tests for the depth I've demonstrated in 1.6, so
there might be value in doing so, but otherwise, I think this can be
marked as invalid/duplicate/shutup-its-fixed.
--
Ticket URL: <https://code.djangoproject.com/ticket/20002#comment:1>
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
