Opened 8 years ago

Closed 8 years ago

#23493 closed New feature (fixed)

Defining bilateral lookup transformations

Reported by: Thomas Chaumeny Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


With the current Transform API, transformations are applied to the left-hand side of the lookup only.

For instance, if you define some unaccent Transform performing the SQL operation UNACCENT(...), the query below won't return an Author with first name Jérémie. Actually, it won't ever return anything.


I think it would be great to be able to define custom transformations which would apply to both sides of the lookup. This would be particularly helpful when you want to perform some lookup insensitive to some SQL transformation (unaccent or other).

Change History (4)

comment:1 Changed 8 years ago by Anssi Kääriäinen

Triage Stage: UnreviewedAccepted

I am going to mark this as accepted assuming the API is opt-in. We already have a precedence of doing this for lower lookup. We could actually remove the lower lookup from Django, and replace it with a bilateral transform.

comment:2 Changed 8 years ago by Tim Graham

Triage Stage: AcceptedReady for checkin
Type: UncategorizedNew feature

Needs a more thorough ORM review, but looking good to me.

comment:3 Changed 8 years ago by Thomas Chaumeny

I updated the PR with a specific error message when trying to apply a bilateral transformation to a nested QuerySet (see — thanks to akaariai for pointing out this case.

We cannot handle a nested QuerySet as we would have to "push" our transformation into that QuerySet, which would require some tricky code for a very unusual use case.

comment:4 Changed 8 years ago by Anssi Kääriäinen <akaariai@…>

Resolution: fixed
Status: newclosed

In 00aa562884a418c4ee20e223ab82c3455997ee7d:

Fixed #23493 -- Added bilateral attribute to Transform

Note: See TracTickets for help on using tickets.
Back to Top