#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
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"66fed37ecb78daf0a50e95151a752b5760293514" 66fed37]:
{{{#!CommitTicketReference repository=""
revision="66fed37ecb78daf0a50e95151a752b5760293514"
Fixed #36689 -- Fixed top-level JSONField __in lookup failures on MySQL
and Oracle.
Added a JSONIn lookup to handle correct serialization and extraction
for JSONField top-level __in queries on backends without native JSON
support. KeyTransformIn now subclasses JSONIn.
Co-authored-by: Jacob Walls <[email protected]>
Thanks Jacob Walls for the report and review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36689#comment:11>
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/0107019b0a7148e3-9613c6d4-a303-412d-8b95-b0a7db3fe45f-000000%40eu-central-1.amazonses.com.
