#29998: pk setup for MTI to parent get confused by multiple OneToOne references.
-------------------------------------+-------------------------------------
     Reporter:  Mārtiņš Šulcs        |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  2.1
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 That seems to be a bug, managed to reproduce.

 Does the error go away if you add `primary_key=True` to `document_ptr`
 like I assume you wanted to do? This makes me realized that the
 [https://docs.djangoproject.com/en/2.1/topics/db/models/#multi-table-
 inheritance MTI documentation] is not completely correcy,
 
[https://github.com/django/django/blob/7d1123e5ada60963ba3c708a8932e57342278706/django/db/models/options.py#L225-L244
 the automatically added `place_ptr` field end up with `primary_key=True`].

 Not sure why we're not checking `and field.remote_field.parent_link` on
 
[https://github.com/django/django/blob/7d1123e5ada60963ba3c708a8932e57342278706/django/db/models/base.py#L183
 parent links connection].

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29998#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 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/065.196991a5d39e721b4f10c8eddda0eabd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to