#29574: Django Foreign Key Mismatch
----------------------------+--------------------------------------
Reporter: josephbiko | Owner: (none)
Type: Bug | Status: closed
Component: Migrations | Version: 2.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => needsinfo
* component: Uncategorized => Migrations
* type: Uncategorized => Bug
Comment:
Hello josephbiko,
I assume you meant that running `makemigrations` between your two model
scenarios doesn't generate the appropriate database alterations?
There's a few bugs (#23521, #25247) related to switching from concrete to
abstract inheritance but in the abstract to concrete case there shouldn't
be any problem as `C.fk`should be automatically repointed to `B.a_ptr`
when `A` is made concrete.
I'm afraid we'll need a more detailed reproduction test case in order to
reproduce your issue. Please include tracebacks and detail every steps
your perform to get there.
--
Ticket URL: <https://code.djangoproject.com/ticket/29574#comment:3>
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/068.45c7254f385e2bd958ae098dc38c6d8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
