Closed matt-schwartz closed 10 years ago
Would you have any interest in RQB support "NOT (a=b AND b=c)"?
i.e. try and support every operator offering "NOT"?
maybe "not in" is a special case. Not sure I'd want to inflict a generic "NOT" on end users.
I think "NOT IN" is a common case and easier to handle (just like "<>"). I don't think every other use of "NOT" would be as useful or as common. For my app I can live without NOT entirely, but "NOT IN" would be nice to have.
Leaning towards a boolean flag on the operator. Something like "support NOT". So then would work with NOT BETWEEN, NOT AND etc (one day).
Took me a while but I've ended up where you started. Bit fragile as depends on prefix being exactly "NOT " (note single whitespace).
Please could you try http://0-6-0.redquerybuilder.appspot.com/
If OK I'll make more robust.
If I use NOT IN, like
It generates good SQL, but that SQL fails when passed into
RedQueryBuilderFactory.create
. The console says171 is the start of "NOT".