Hello, I have a simple cypher query with a WHERE clause and not other logic that looks something like: WHERE node.propValue = 'string value with spaces' Replacing the "=" with CONTAINS, STARTS WITH, ENDS WITH, and TRIM() returns the expected results without changing the value right of the equals s…

What happened to the latest posts? Anyway, when you outputted the characters, what did the ellipses represent? Did you get every character, and only those, from the literal string?

@TrevorS , you marked a solution but this is not resolved yet. The post you marked is a troubleshooting step. Please unmark.

Running the two cypher statements sequentially, a match was returned. What does the property look like when you return it? create(m:String) set m.propValue = 'string value with spaces'; match(m:String) where m.propValue = 'string value with spaces' return m

No idea what happened to those other posts. Hopefully a moderator can get them back because they were useful for context. Correct. Every character, including spaces, from the literal string were returned and nothing more. Not sure if you saw, but using toString(node.propValue) also returns expected…

My apologies @tk . I removed the solution from the post.

When I return the value, there is no difference between the output and what I have in the where clause when I used the "=". I even exported the result produced when using the CONTAINS to CSV, opened in Notepad++ to ensure no special characters, etc. , re-pasted the value in the query and re-ran with…

I dont see any posts missing from the thread here. The last I can see is the link below. https://community.neo4j.com/t5/neo4j-graph-platform/string-equality-not-returning-expected-results/m-p/57587/highlight/true#M34295

me too. So, you get a result returned with all three: 'contains', 'starts with', and 'ends with'? The only way that is possible is if the string is equal to the literal value or the string is a concatenation of the literal value, any literal string, and the literal value. That of course, is not th…

You are correct; I get the expected results when using 'contains', 'starts with', and 'ends with' but also when using toString and trim functions on node.propValue After running the above in my environment I get the expected results of: "s" "t" "r" "i" "n" "g" "" "v" "a" "l" ... ... ..…

STRING Equality Not Returning Expected Results

Neo4j Graph Platform

glilienfield (Gary Lilienfield) July 12, 2022, 12:38am 14

I don't have any further suggestions. If the property's value is the same character-by-character, then the property and the literal string should be equal. Maybe raise it as a defect with Neo4j.

Topic		Replies	Views
Filtering Query Results Neo4j Website	0	462	August 5, 2020
Exact match for string with CONTAINS Neo4j Graph Platform migrated	3	579	December 5, 2022
Cypher query for equality returning false but it is true Cypher	3	75	June 21, 2024
Using case statement Neo4j Graph Platform cypher	2	5871	May 4, 2019
Query example for trying to find nodes which ends with similar word Cypher querying , cypher	8	342	February 9, 2022

STRING Equality Not Returning Expected Results

Related topics