#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):
FWIW my patch currently fails with this exception (tested by Senthil
Kumaran, cf debian bug):
{{{
File "/usr/lib/python2.7/dist-packages/django/db/migrations/loader.py",
line 291, in check_consistent_history
if fake_initial and self.detect_soft_applied(None, parent):
File "/usr/lib/python2.7/dist-packages/django/db/migrations/loader.py",
line 343, in detect_soft_applied
if migration.initial is None:
AttributeError: 'Node' object has no attribute 'initial'
}}}
Do you know how I can get the correct Migration object from a Node object?
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#comment:6>
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.dfca124083c0ae18fdc8dbd71e8af099%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
