FILTER with '&&' and '||' not supported

[niklas88]

Trying to use the current QLever version with the new parser in conjunction with Aqqu results in an error e.g. for the following query.

PREFIX fb: <http://rdf.freebase.com/ns/>

SELECT (COUNT(?1) AS ?count) WHERE {
 fb:m.01jrbb fb:film.film.starring ?0 .
 ?0 fb:film.performance.character fb:m.02_29cg .
 ?0 fb:film.performance.actor ?1 .
 FILTER (?1 != fb:m.02_29cg && ?1 != fb:m.01jrbb)
}
LIMIT 30000

This is because it doesn't support &&. It also doesn't seem to support ||. It looks like this was actually not supported in the older parser either but that was so lax that the query was still accepted and whatever it did was good enough for Aqqu.

I'll change Aqqu to use separate FILTER but we should still support && and || in the future.

[graue70]

Workaround for && is using two separate FILTER statements (as Niklas mentioned).
I don't know an easy workaround for ||.

[ikabadzhov]

Shouldn't || come from DeMorgan's law ((A || B) == !(!A && !B)) or am I missing something? That is then, two FILTER statements checking the opposite condition, followed by some MINUS equivalent operator for QLever.

[hannahbast]

The expression code has been completely rewritten last year and this now works.