#23731: PointField does not allow setting blank=True and null=False
---------------------------------+-------------------------------------
Reporter: raratiru | Owner: timgraham
Type: Bug | Status: closed
Component: GIS | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: PointField, gis | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"17205a98ed0e4fb2a4ce9137508ee65efc448c07"]:
{{{
#!CommitTicketReference repository=""
revision="17205a98ed0e4fb2a4ce9137508ee65efc448c07"
[1.7.x] Fixed #23731 -- Fixed migrations crash when adding blank
GeometryFields on PostGIS.
Thanks raratiru for the report and Claude Paroz for review.
Backport of d6d55368d4 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23731#comment:6>
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/066.480fec58cd439fb617274036b98e2c85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.