#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 Zanuda999):
I created model like
from django.db import models
class Test(models.Model):
text1 = models.CharField(null=True, blank=True, max_length=255)
text2 = models.CharField(null=True, blank=True, max_length=255)
then i created initial migration, migrated, created 2 objects with null
values in text1 and text2, changed all fields to null=False, blank=False,
migrated and all is ok. i have installed postgresql 9.4.2
--
Ticket URL: <https://code.djangoproject.com/ticket/25105#comment:2>
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.7fa565b749c6db96ddb1a9c7b410f077%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
