#20776: Multi-level Multi-table Inheritance - mismatched PKs / explicit
db_columns
-------------------------------------+-------------------------------------
Reporter: dowstreet@… | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.5
Severity: Normal | Resolution:
Keywords: Muti-table | Triage Stage:
Inheritance | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I believe the problem is having level2_id in Level2, and level2
OneToOneField in Level3. OneToOneFields store the related instance in
field.name (level2) and the raw database value in field.attname
(level2_id). The level2 field's attname conflicts with level2_id field
name in Level2.
I am not 100% sure if this is the case. You could test this by changing
the name of level2_id to something else in Level2. If the reason is the
naming conflict this looks like something that could be dealt with in the
validation GSoC project.
--
Ticket URL: <https://code.djangoproject.com/ticket/20776#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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/079.a002e455f50566f07ff036c4f9b5238f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
