#21554: incorrect SQL generated when using multiple inheritance -------------------------------------+------------------------------------- Reporter: pegler | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: master (models, ORM) | Resolution: Severity: Normal | Triage Stage: Accepted Keywords: multiple- | Needs documentation: 0 inheritance | Patch needs improvement: 1 Has patch: 1 | UI/UX: 0 Needs tests: 0 | Easy pickings: 0 | -------------------------------------+------------------------------------- Changes (by mitchell):
* status: closed => new * resolution: fixed => Comment: Test needs to be extended to test that the title is correct. Currently the patch replaces all fields from non-primary classes with the ID. Also, the second base was not being joined to the query correctly. Second pull request here: https://github.com/django/django/pull/2059 -- Ticket URL: <https://code.djangoproject.com/ticket/21554#comment:8> 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.5e9aaa58ea4f5141b9656c48e4b2465b%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.