#25771: Serialization of natural foreign key in migration scripts does not work
-------------------------------------+-------------------------------------
Reporter: bowensong | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution:
Keywords: database migration | Triage Stage:
serialization | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think this is expected behavior because the `natural_key()` method isn't
available in migrations. Per
[https://docs.djangoproject.com/en/dev/topics/migrations/#historical-
models the docs], "Because it’s impossible to serialize arbitrary Python
code, these historical models will not have any custom methods that you
have defined."
--
Ticket URL: <https://code.djangoproject.com/ticket/25771#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/067.b10c200d4cd26fea10d2f233372f9268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
