#29058: Adding 'null=True' to a PointField doesn't create working migration
-------------------------------------+-------------------------------------
Reporter: Yaman Ozakin | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 1.11
Severity: Normal | Resolution:
Keywords: geodjango, | Triage Stage: Accepted
pointfield |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jani Tiainen):
This is actually more widespread problem with spatialite backend.
DB geometry field in spatialite backend is defined as None which causes
any kind of migration, even just adding verbose name which doesn't change
field type nor anything database related to cause error message.
All other spatial backends seem to return at least some kind of a db field
type.
--
Ticket URL: <https://code.djangoproject.com/ticket/29058#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/067.c73f3ee81b4cdda3584e669385165cac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
