#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: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Matt Westcott):
* cc: Matt Westcott (added)
Comment:
In case it hasn't already been noted - the example above did previously
work in 2.2, and the error is a regression in 2.2.1, specifically this
commit:
https://github.com/django/django/commit/88bf635c356b4d3a47e88dc4142b90060ce3c2ef
. As such, I think this might justify being upgraded to a bug.
(FWIW, we encountered this independently here:
https://github.com/wagtail/wagtail/issues/5547)
--
Ticket URL: <https://code.djangoproject.com/ticket/30446#comment:6>
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.c2780bdfa13dfff0debfa5ae8cee928a%40djangoproject.com.
