Changes between Version 1 and Version 2 of Ticket #35413, comment 2


Ignore:
Timestamp:
May 26, 2024, 11:02:49 AM (8 weeks ago)
Author:
Amir Karimi

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35413, comment 2

    v1 v2  
    22> Replicated, this is also true of other fields.
    33> I agree that saying something like `Unsupported lookup 'gt__foo'`, `Unsupported lookup 'gt__'`, and `Unsupported lookup 'gt__lt'` would be clearer.
    4 If we just pass down `LOOKUP_SEP.join(arg.split(LOOKUP_SEP)[1:])` to the `build_lookup` method, it can print out the input lookup entirely. It outputs`'gt__foo'`, `'gt__' `, and `'gt__lt' `.
     4If we just pass down `LOOKUP_SEP.join(arg.split(LOOKUP_SEP)[1:])` to the `build_lookup` method in `django/db/models/sql/query.py`, it can print out the input lookup entirely. It outputs`'gt__foo'`, `'gt__' `, and `'gt__lt' `.
    55
    66It can be an argument to the `try_transform` method. Not sure whether `name` is needed or not. Thoughts?
     7BTW, I can handle it.
Back to Top