#31967: Resolving an output_field for mixed types crashes in database functions.
-------------------------------+------------------------------------
Reporter: Matt Hegarty | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: master
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
-------------------------------+------------------------------------
Changes (by felixxm):
* component: Database layer (models, ORM) => Documentation
* severity: Release blocker => Normal
Comment:
We didn't resolve output fields for `Value()` expressions before
1e38f1191de21b6e96736f58df57dfb851a28c1f, so they were ignored when
resolving an output field for functions. Now, we take them into account,
that's why an error is raised. IMO it's an expected behavior. It should be
enough to mention this in release notes.
You can fix this by using `Decimal('0')`, e.g.
`Coalesce(F('field_decimal'), Decimal('0')))`
--
Ticket URL: <https://code.djangoproject.com/ticket/31967#comment:4>
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/072.475eb2820db60d58e53b821a5ef9dc94%40djangoproject.com.
