#30971: Query.resolve_lookup_value coerces value of type list to tuple
-------------------------------------+-------------------------------------
Reporter: George | Owner: nobody
Marshall |
Type: Bug | Status: new
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes introduced in #30687 cause an input value `list` to be coerced to
`tuple` breaking exact value queries. This affects ORM field types that
are dependent on matching input types such as `PickledField`.
The expected iterable return type should match input iterable type.
--
Ticket URL: <https://code.djangoproject.com/ticket/30971>
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/048.8864c5efba2f0d1a0cfdaf45d403027e%40djangoproject.com.
