NRQL allowing Where in Where

Hello fellow Relics!

This is hopefully a quick one, I was expecting the NRQL editor to complain about this kind of syntax;

SELECT count(message) FROM Log WHERE condition1 = 'xxx' WHERE condition2 LIKE '%yyy%'

But it appears to run successfully until used as an alert where it never closes based on the condition - as if only one of the WHERE’s is processed.

I’m in the process of testing the change of the second WHERE to an AND as it should have been from the beginning.

I’m currently assuming “loss of signal” is not part of the mix at this stage as I’m always receiving a count of zero when not triggered and following a successful trigger.

Is there a reason this syntax does not raise an error when been created?