#25105: Migrating multiple CharFields to null=False breaks on PostgreSQL
--------------------------------+------------------------------------
Reporter: Daniel Roseman | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Comment (by Simon Charette):
It looks like using an approach similar to #25492
(cd7efa20338cb6f3ede4780e00590c0a6dd48ca2) could work here.
We should be checking all deferred constraints (Django only creates
deferred constraint for foreign keys AFAIK) on tables we perform `UPDATE`
on.
An easy solution would be to append `';SET CONSTRAINTS ALL IMMEDIATE;SET
CONSTRAINTS ALL DEFERRED'` to Postgres' schema editor
`sql_update_with_default` attribute to force a constraint check. Postgres
should be smart enough to only check the required tables, something I
noticed when implementing support for the `table_names` parameter of the
`check_constraint` function.
--
Ticket URL: <https://code.djangoproject.com/ticket/25105#comment:7>
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/065.637f81e736d5c8ad3b0248350e7ab115%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
