#34838: GeoDjango database functions incompatible with GeneratedField
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: Paolo
| Melchiorre
Type: Bug | Status: assigned
Component: GIS | Version: dev
Severity: Release blocker | Resolution:
Keywords: field, database, | Triage Stage: Accepted
generated, gis, feodjango |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I suspect we'll want to avoid adding many `output_field = field; if
field.generated: field.output_field` all over the codebase and that we
should favour an approach where expression resolving (see
`sql.query.Query.resolve_ref`) returns a `Col` with the proper
`output_field`.
Maybe this can be done at the `GeneratedField.get_col` level?
--
Ticket URL: <https://code.djangoproject.com/ticket/34838#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a8ff881a3-67950d30-dd03-4178-b7d7-9565e36d1bae-000000%40eu-central-1.amazonses.com.
