rql #34440 fix rule order so 'HAVING (X op Y)' is now parseable while 'HAVING (1+2) op Y' isn't anymore parseable [resolved]

prioritynormal
typebug
done in0.26.2
load0.200
load left0.000
closed by<not specified>