#24303: Not all models available in custom data migration
---------------------------------+--------------------------------------
Reporter: grandfatha | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: worksforme
Keywords: data migrations | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by grandfatha):
Oh god that was a bad idea. If anyone ever reads this: Use a real
migration instead of "__first__" if your data migration requires fields
that will be added after "__first__". It might sound nice to not depend on
a specific version, but it can cause failure.
--
Ticket URL: <https://code.djangoproject.com/ticket/24303#comment:4>
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.302963f55d957c8dfcfd3a4b0f0f89ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
