#36689: Top-level __in lookup on JSONField fails on MySQL, Oracle
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Clifford
| Gama
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: JSON, In | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"7b54ddd5e64c96c641b70bb5f0e958a9e2035fb2" 7b54ddd]:
{{{#!CommitTicketReference repository=""
revision="7b54ddd5e64c96c641b70bb5f0e958a9e2035fb2"
Refs #36025 -- Made get_prep_lookup() pass output_field when wrapping
direct values in Value.
Previously, only strings were supplied with an output_field when wrapping
direct value iterable elements in Value expressions for ExpressionList.
This
caused problems for __in lookups on JSONField when using expressions
alongside direct values, as JSONField values can have different types
which
need to be adapted by the field's get_db_prep_value().
Refs #36689.
Thanks Jacob Walls for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36689#comment:13>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b0a714973-a5a5709b-46bc-4c15-b454-8b543d0b440c-000000%40eu-central-1.amazonses.com.
