#30896: MySQLdb._exceptions.OperationalError: (1054, "Unknown column ...) error
when `migrate --database=newfreshdb`
--------------------------------------+------------------------
Reporter: coolnodje | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------
I keep hitting this problem while trying to replay an entire database
migrations on a new fresh DB (from MySQL to PostgreSQL to be precise).
MySQL complains of a non existing column that was removed in a later stage
of migrations.
This column doesn't exist in MySQL anymore as it is up to date with the
newest migration. So it's only natural that the column cannot be found.
The question is: why is `migrate` looking for this column at this stage?
It can only be found in the target new DB.
I'm not including any code at this stage but I guess I can probably find a
way to share the whole migrations if this doesn't sound like an already
addressed problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/30896>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.6c64e3f3945c0abcf9f5d774e28e5f7d%40djangoproject.com.
