#30971: Query.resolve_lookup_value coerces value of type list to tuple
-------------------------------------+-------------------------------------
Reporter: George Marshall | Owner: George
| Marshall
Type: Bug | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by George Marshall):
* has_patch: 0 => 1
Comment:
PR: https://github.com/django/django/pull/12050
This could potentially use a test case, need some direction on how to
cover this.
I have also included links to my Django library code that was affected by
the change.
https://github.com/georgemarshall/django-
cryptography/blob/789e7a757e01220bc46b17b995bb201cda496ef6/tests/fields/test_pickle.py#L61
https://travis-ci.org/georgemarshall/django-cryptography/jobs/609869188
I am also not sure how the postgres `ArrayField` was not affected by the
tuple coercion.
--
Ticket URL: <https://code.djangoproject.com/ticket/30971#comment:2>
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.b7837407ed597ad09bad45056f7f9cb0%40djangoproject.com.
