#23738: Migrations broken with django 1.7.1 when changing null from true to
false.
----------------------------+--------------------------------------
Reporter: niwibe | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by niwibe):
We are using the psycopg2 backend.
Tomorrow I'll try to make a small project for make easy to reproduce it.
But the process is very simple:
- havind django 1.7, I have created a migration to one model that already
have one integer field with null=True, blank=True and default=0 on first
migration, changing null and blank parameters both to False.
- update to django 1.7.1
- try apply the created migration
--
Ticket URL: <https://code.djangoproject.com/ticket/23738#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/064.75bcfe7037f3f336f2e95817a6a7eda3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
