NONE BETWEEN has incorrect behavior

[sync-by-unito]

In RQL, you are allowed to use the array operators <ALL/NONE/ANY> with BETWEEN. The way RQL parses the BETWEEN operator is to make it into a >= AND <=. For example, x BETWEEN {0, 10} gets parsed to {}x >= 0 AND x <= 10{}. This presents issues in conjunction with the NONE operator, since a query like NONE x BETWEEN {0, 10} will get parsed to {}NONE x >= 0 AND NONE x <= 10{}, which does not correctly represent the intention of the NONE query (for example, -1 would not match since it is <= 10 even though it is outside of the BETWEEN range)

[sync-by-unito]

➤ On 2022-04-22, Jørgen Edelbo commented:

The support for BETWEEN was only done an an afterthought, and the use on NONE is apparently not working as expected. It will require substantial work to implement it properly, so short term we should probably just not allow it to be used.

[sync-by-unito]

➤ On 2022-05-03, Ben Redmond commented:

This sounds good to me. I merged a change to explicitly disallow NONE BETWEEN queries on the server. Can we make a similar change on the client side as well?

[sync-by-unito]

➤ On 2022-05-04, Jørgen Edelbo commented:

Yes, that should be a small change.

[sync-by-unito]

➤ Jørgen Edelbo commented:

[~[email protected]] I found out that ANY had a similar problem, so I disallowed that as well.