We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm running the following query:
RETURN ( ( ( 7414 IN [7372, 7414] ) AND ( 67542.0 <= 64547.0 ) ) OR ( ( 7414 IN [7371, 7368, 7413, 7410] ) AND ( 67542.0 <= 4061660.0 ) ) );
On
false
But! On
true
This bunch of numbers is a heavily reduced part of my match-where query, which matched more nodes than expected.
Is this a bug? Or am I just missing something about the Cypher's syntax?
The text was updated successfully, but these errors were encountered:
Neo4j version: 3.4.1 Operating system: Ubuntu 16.04 Connecting through [http://localhost:7474/browser/] -- also true
Sorry, something went wrong.
RETURN ( ( ( 7414 IN [7372, 7414] ) AND ( 67542.0 <= 64547.0 ) ) OR ( ( 7414 IN [7371, 7368, 7413, 7410] ) AND ( 67542.0 <= 4061660.0 ) ) ), ( ( 7414 IN [7372, 7414] ) AND ( 67542.0 <= 64547.0 ) ), ( 7414 IN [7371, 7368, 7413, 7410] ) AND ( 67542.0 <= 4061660.0 ), false OR false;
-- true, false, false, false on 3.4.7
true, false, false, false
And on v. 3.3.2 no problem.
Hej @hakami1024 ,
Thanks for reporting this. We will take a look!
Cheers, Sascha
Neo4j Cypher Team
even shorter (in 3.4.0 and 3.4.7):
return ( ( "a" IN ["a", "b"] ) AND false ) OR ( "X" IN ["c", "d"] ) ; => false
return ( ( "a" IN ["a", "b"] ) AND false ) OR ( "a" IN ["c", "d"] ) ; => true
72fd3ba
SaschaPeukert
No branches or pull requests
I'm running the following query:
On
it returns
false
. That looks OK.But!
On
it returns
true
.This bunch of numbers is a heavily reduced part of my match-where query, which matched more nodes than expected.
Is this a bug? Or am I just missing something about the Cypher's syntax?
The text was updated successfully, but these errors were encountered: