#24853: FK value not inserted in database in data migration
-------------------------------------+-------------------------------------
Reporter: rakanalh | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database, | Triage Stage:
migrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
I think the problem is roughly described in
[https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies the
dependencies section] of the migrations docs. Basically, migrations and
models without migrations don't interact very well.
I don't think we are going to invest any time in trying to remedy this as
migrations will be compulsory for all apps in 1.9. We could add a sentence
to the 1.8 docs in the dependencies section, "In addition, any models that
are used in RunPython operations must have migrations."
--
Ticket URL: <https://code.djangoproject.com/ticket/24853#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/066.ca8cfd003224dec9045274cd127fa459%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
