#16732: Unable to have abstract model with unique_together
-------------------------------------+-------------------------------------
Reporter: Mitar | Owner: Can
| Sarıgöl
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Can Sarıgöl):
* status: new => assigned
* owner: nobody => Can Sarıgöl
* has_patch: 0 => 1
* version: 1.3 => master
Comment:
[https://github.com/django/django/pull/11499 PR]
When I read the document about
[https://docs.djangoproject.com/en/2.2/topics/db/models/#meta-inheritance
meta-inheritance], I didn't see the topic that in {{{ abstract = False }}}
case What happens to child meta? as far as I could see from
[https://github.com/django/django/blob/a9179ab032cda80801e7f67ef20db5ee60989f21/django/db/models/base.py#L144
code], {{{ordering}}} and {{{get_latest_by}}} always moving in child meta
in every situation. Should we change the code like my PR + document about
{{{ abstract = False }} and fix the blown up test?
--
Ticket URL: <https://code.djangoproject.com/ticket/16732#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.e3d04b660cf3d72292581de000fd4a1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
