#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 Claude Paroz):
I'm not the best specialist on Django migrations, but I guess when things
go wrong this way, some manual intervention is required.
I would suggest a custom repair script along these lines (absolutely
untested) which should add the missing line in the migrations table:
{{{
from django.db.migrations.recorder import MigrationRecorder
from django.db import DEFAULT_DB_ALIAS, connections
connection = connections[DEFAULT_DB_ALIAS]
recorder = MigrationRecorder(connection)
recorder.record_applied('linaro_django_xmlrpc', '0001_initial')
}}}
I'll let others answer about whether this is a bug Django could fix, like
providing an option like "I know things are broken, I know what I'm doing,
please do not check migrations consistency"!
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#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/063.b961ab95c5b10193a1ac06f96533dcc6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
