#31936: On MySQL, Oracle, and SQLite, __in lookup doesn't work on key
transforms.
-------------------------------------+-------------------------------------
Reporter: Sébastien Pattyn | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: JSONField SQLite | Triage Stage: Accepted
MySQL |
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:"9075d1f662f8734004d0207a58927c93d2b19092" 9075d1f6]:
{{{
#!CommitTicketReference repository=""
revision="9075d1f662f8734004d0207a58927c93d2b19092"
[3.1.x] Fixed #31936 -- Fixed __in lookup on key transforms for JSONField.
This resolves an issue on databases without a native JSONField
(MariaDB, MySQL, SQLite, Oracle), where values must be wrapped.
Thanks Sébastien Pattyn for the report.
Backport of 1251772cb83aa4106f526fe00738e51c0eb59122 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31936#comment:10>
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/075.7cb762379201e088514d04326b05e44b%40djangoproject.com.