#36934: BuiltinLookup breaks with params-as-a-tuple in django 6.0
-------------------------------------+-------------------------------------
Reporter: Stefan Bühler | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
> What do you mean "Your link doesn't go to a custom lookup"?
You're right that my statement lacked some precision. Your link goes to a
mixin that is inherited by custom lookups with no further customization,
which was not what I was expecting to see. I was expecting to see a custom
lookup that was manipulating parameters, like #36922. Instead, the mixin
only manipulates the SQL statements. So, if there is a bug here, it would
seem possible to construct it without django-netfields or any third party
package. That would be a slam-dunk case for backporting, no question about
it. This is why I wanted to see the stacktrace, including the original
queryset call that reproduced the issue. That would indeed be
"interesting". I'm even volunteering to reverse engineer the problematic
queryset call, but I need a place to start.
Until someone can provide that, I can't move this forward.
> Also it is just obvious from the code it can't work that way.
> BuiltinLookup.as_sql (and YearLookup.as_sql) really needs to handle
tuple params from process_lhs.
Sorry, it's not obvious to me. `BuiltinLookup.as_sql` returns a list of
params in Django 6.0. Where is a tuple returned? From a custom lookup?
(I'm begging someone to show me.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36934#comment:4>
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/0107019c7649553a-2ceb9e10-1580-4c7a-96e7-f54ace7e4af1-000000%40eu-central-1.amazonses.com.
