#28250: migration depending on non-existing legacy migration
-------------------------------+--------------------------------------
Reporter: Brian May | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Raphaël Hertzog):
I have not looked very closely yet, but shouldn't the check added in
#25850 be loosened for this specific case, just like it has been loosened
in #27004 for squashed migrations?
I don't see why 1.10 or 1.11 should refuse to fake a migration that 1.8
was able to fake properly.
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#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/063.0fef51f0ebd06810e0154351d28379f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
