@@ -233,16 +233,16 @@ def lookup_op(node_value, comp_value):
233233
234234 if isinstance (comp_value , bool ) and op == "iexact" :
235235 # Use "exact" for boolean values, as certain DB drivers (e.g., Postgres) will transpile
236- # "<field> iexact true/false" to "UPPER(field::text) = UPPER(true/false), which fails.
237- # UPPER requires a string.
236+ # "<field> iexact true/false" to "UPPER(field::text) = UPPER(true/false), which fails.
237+ # UPPER requires a string.
238238 return "exact"
239239 if comp_value == "" and op == "iexact" :
240240 # In Oracle iexact + empty string will never evaluate to true. I.e., TRIM(' ') != '' and
241- # UPPER(TRIM('')) != UPPER(''). Furthermore, case-insensitive search against an empty
242- # string has no added value over a case-sensitive search. Hence, whenever the SCIM
243- # path is '<field> eq ""', rather than doing field__iexact='', we do field=''. The
244- # oracle Django driver will then convert field='' into "field" IS NULL, which is the
245- # correct way to do it in Oracle.
241+ # UPPER(TRIM('')) != UPPER(''). Furthermore, case-insensitive search against an empty
242+ # string has no added value over a case-sensitive search. Hence, whenever the SCIM
243+ # path is '<field> eq ""', rather than doing field__iexact='', we do field=''. The
244+ # oracle Django driver will then convert field='' into "field" IS NULL, which is the
245+ # correct way to do it in Oracle.
246246 return "exact"
247247
248248 return op or node_value
0 commit comments