#23719: GIS test failure with MySQL 5.6: BLOB/TEXT column can't have a default
value
---------------------------+-------------------------------------
Reporter: timgraham | Owner: timgraham
Type: Bug | Status: assigned
Component: GIS | Version: 1.7
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 timgraham):
You can have something like `CharField(default='foo')` since model field
defaults aren't applied at the database level. [1d3d01b4] prevents
temporarily setting a default on MySQL to prevent the same error as this
ticket for Char/TextField.
Is `PointField(default=???)` a possibility? If so, it seems your proposal
wouldn't solve the issue entirely. We'd need something like
[https://github.com/timgraham/django/compare/23719 my initial proposal]
(possibly using `isinstance(field, GeometryField)` instead). I think your
proposal may address #23581 though. I will look at that later today.
--
Ticket URL: <https://code.djangoproject.com/ticket/23719#comment:5>
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.9fc668ad489b2f7901777642915837db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
