#29503: Order of parameters pass to __in lookup affected by de-duplication.
-------------------------------------+-------------------------------------
Reporter: Nick Pope | Owner: Nick Pope
Type: Bug | Status: assigned
Component: Database layer | Version: 1.11
(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
-------------------------------------+-------------------------------------
Comment (by Nick Pope):
Replying to [comment:2 Tim Graham]:
> What practical problem did you encounter? I'm surprised that the order
of items in an `IN` clause would matter much.
Heh. I get the feeling that I'm going to get shot down here (and I know
and understand the reasons why).
I've inherited some code that currently and for the foreseeable future
depends on the output of the query generated by `Query.sql_with_params()`.
It executes it via `pandas.DataFrame.read_sql_query()` and also uses this
to generate a cache key. Because the parameter ordering is unstable, this
affects the key generation.
Regardless of the horrors of this, the issue looks like a regression to me
- the previous behaviour changed unexpectedly. I can understand if you'd
like to only apply this to master, however.
--
Ticket URL: <https://code.djangoproject.com/ticket/29503#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.17f92072fa1c6a358273b86310bac614%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
