Preparation for Filter Expressions/Expression Filters. #10098
Conversation
This is in preparation for django#8119. In order to make it possible to have different behaviour when an expression is to be used _only_ in a WHERE clause, we need to have some tag on the expression. I think maybe we need to make the resolve_expression() accept arbitrary kwargs - it's either that or just add for_where=False.
|
@timgraham You mentioned in the related PR about a deprecation - I can't see how to do a deprecation on an added field. Any suggestions? |
|
Okay, I bit off more than I can chew tonight with this. I need to re-think how this can be fixed to allow existing code to work. |
|
I think the deprecation for supporting |
|
Hmm. I've spent a bit of time looking at this, and I'm not sure that moving to I did note that in #7615 there is the addition of an argument to |
|
I've struggled to actually get this to work. I am not sure I have a passing test run (or am even close to it). |
|
what difficulties you are facing? |
|
I don't think this is the best approach. I'm closing this PR. |
This is in preparation for #8119.
In order to make it possible to have different behaviour when an
expression is to be used only in a WHERE clause, we need to have
some tag on the expression.
I think maybe we need to make the resolve_expression() accept arbitrary
kwargs - it's either that or just add for_where=False.