#36893: MigrationWriter doesn't serialise elidable kwarg
-----------------------------------+--------------------------------------
Reporter: lgreville | Type: Bug
Status: new | Component: Migrations
Version: 6.0 | Severity: Normal
Keywords: migrations runsql | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------------+--------------------------------------
If a migration has elidable RunSQL operations and is serialised by
MigrationWriter, they will be serialised without the elidable kwarg. This
means they will now be treated as unelidable.
This issue came up for me recently when automatically generating a
migration to remove stale tables/columns: the generated migration contains
elidable RunSQL operations to drop the stale data, but when they are
serialised they are no longer marked as elidable.
This has likely not cropped up before, as MigrationWriter is typically
used by the squash command, which never needs to write the operation
(cause it gets thrown away if it's elidable).
Someone from my company can pick this up if it's accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/36893>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019c0d120a91-d87be064-5d84-4929-a40a-1ede5992dbdd-000000%40eu-central-1.amazonses.com.
