#14462: Aggregates default to the database type instead of the field type
-------------------------------------+-------------------------------------
Reporter: WoLpH | Owner: wogan
Type: Bug | Status: closed
Component: Database layer | Version: 1.2
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: aggregate, | Needs documentation: 0
annotate, type, coerce | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"e9103402c0fa873aea58a6a11dba510cd308cb84"]:
{{{
#!CommitTicketReference repository=""
revision="e9103402c0fa873aea58a6a11dba510cd308cb84"
Fixed #18757, #14462, #21565 -- Reworked database-python type conversions
Complete rework of translating data values from database
Deprecation of SubfieldBase, removal of resolve_columns and
convert_values in favour of a more general converter based approach and
public API Field.from_db_value(). Now works seamlessly with aggregation,
.values() and raw queries.
Thanks to akaariai in particular for extensive advice and inspiration,
also to shaib, manfre and timograham for their reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14462#comment:7>
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/063.5bfa92500ad0c69d760740ab2d067e8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
