#34838: GeoDjango database functions incompatible with GeneratedField
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: Paolo
| Melchiorre
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: field, database, | Triage Stage: Ready for
generated, output_field | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"14ab15d69ab2171ef26b295dcbd561b723b7eb7e" 14ab15d6]:
{{{#!CommitTicketReference repository=""
revision="14ab15d69ab2171ef26b295dcbd561b723b7eb7e"
[5.0.x] Fixed #35344, Refs #34838 -- Corrected output_field of resolved
columns for GeneratedFields in aliased tables.
Thanks Simon Charette for the review.
Backport of 5f180216409d75290478c71ddb0ff8a68c91dc16 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34838#comment:10>
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/0107018e9c5ff6dc-9ff475f2-c4a2-46c7-8cc3-99e12ede33ca-000000%40eu-central-1.amazonses.com.
