#35038: Changing violation_error_message on constraints cause a remove/add
operation in migration
-------------------------------------+-------------------------------------
Reporter: David | Owner: Adrienne
Type: | Franke
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
I think the latest
[https://github.com/django/django/pull/17846#issuecomment-1949371939
consensus] is that we need a new `Operation` for `AlterConstraint` that is
documented to be a no-op (emits no SQL) and that the migration framework
will produce in these cases in order to avoid dropping and recreating
constraints on the database.
--
Ticket URL: <https://code.djangoproject.com/ticket/35038#comment:12>
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/010701917cc6d659-6538a798-2900-4fea-95de-b34447968ad1-000000%40eu-central-1.amazonses.com.
