> You say that
>…
> isn't valid SQL. What's wrong with it? It looks valid and correct to
> me.
Right, this was phrased poorly. I assume this is valid ANSI SQL, but it is not
for the versions of Oracle and SQL Server I’m currently working with. To this
point I haven’t run into any issues
You say that
SELECT code, CASE WHEN code = 'test_val' THEN ABS(val) ELSE NULL END AS absval
FROM TEST
WHERE CASE WHEN code = 'test_val' THEN ABS(val) > 0 ELSE FALSE END
isn't valid SQL. What's wrong with it? It looks valid and correct to
me. (I acknowledge that it's neither pretty nor
I'm having an issue with CoreFilters.FILTER_REDUCE_EXPRESSIONS. I'm wondering
if this is a problem with the rule, or with how I've set up my logical tree.
Conceptually I am trying to use the equivalent of a computed column in a WHERE.
Since this isn't legal:
SELECT code, CASE WHEN code =
