#29751: Saving deserialized objects in custom migration fails in certain cases
-------------------------------------+-------------------------------------
Reporter: 0xKD | Owner: 0xKD
Type: Bug | Status: assigned
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage:
serialize,deserialize,migration | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* component: Database layer (models, ORM) => Migrations
* easy: 1 => 0
Comment:
At first glance this seems plausible.
@0xKD: you've assigned yourself. Can you add a failing test case that
reproduces the issue here?
--
Ticket URL: <https://code.djangoproject.com/ticket/29751#comment:2>
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/062.69f23080cafc81750a85497989a60e26%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
