#30123: Remove support for tuples returned from
DatabaseIntrospection.get_field_type().
-------------------------------------+-------------------------------------
Reporter: Nick Pope | Owner: Nick Pope
Type: | Status: assigned
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Following on from #30115, there are two places where
`DatabaseIntrospection.get_field_type()` returns a tuple pair of the
string name of the field type and a dictionary of extra parameters for the
field type:
1. For the SQLite backend where a field has a size, e.g. `varchar(40)`.
2. For the PostGIS backend where we need to handle `geography` data types.
The SQLite case led to an obscure bug that has been addressed for #30115
by removing it as it turned out that the `max_length` value was already
handled.
This leaves only the PostGIS case which this ticket proposes to replace
with an alternative solution, as well as the removal of workarounds in the
test suite that handle tuples returned from
`DatabaseIntrospection.get_field_type()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30123>
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/050.6518612cddc1e10aea62ee56299eba30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
