#30446: Automatically resolve Value's output_field for stdlib types.
-------------------------------------+-------------------------------------
Reporter: Ozan Gerdaneri | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: SearchVector, | Triage Stage: Accepted
SearchVectorField , Value |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"ea3beb4f5a61870c87ba028369de4d2c2f316ad0" ea3beb4]:
{{{
#!CommitTicketReference repository=""
revision="ea3beb4f5a61870c87ba028369de4d2c2f316ad0"
Refs #30446 -- Defined default output_field of text database functions.
This prevented the default behavior of
BaseExpression._resolve_output_field from error'ing out when such
functions accepted both expressions from mixed types
(e.g. SubStr(CharField, IntegerField, IntegerField)).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30446#comment:8>
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/063.500161a5e32796688c3e7c4c10e02861%40djangoproject.com.
