#25105: Migrating multiple CharFields to null=False breaks on PostgreSQL
----------------------------+------------------------------------
Reporter: danielr | 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 spookylukey):
I've also seen this in production with a '''single''' `AlterField`
migration. I saw this with some Postgres versions (9.1.16) and not others
(9.3.6). I've been able to fix it by manually running `UPDATE foo SET bar
= '' WHERE bar IS NULL;` and re-running the migration.
With other tables in the same DB, simply splitting into one migration per
field is enough to fix it. I haven't been able to investigate further.
--
Ticket URL: <https://code.djangoproject.com/ticket/25105#comment:4>
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.261f6637431692b0f7a9a0803c32f8ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
