Skip to content
New issue

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

Bug due to handling of None value #648

Open
w158937299 opened this issue Jan 19, 2024 · 0 comments
Open

Bug due to handling of None value #648

w158937299 opened this issue Jan 19, 2024 · 0 comments

Comments

@w158937299
Copy link

Agensgraph version: 2.13.0
Operating system: (Windows 11)
API/Driver: (psycopg2 2.9.7)
Steps to reproduce
7

As shown in this picture, this query first matches nodes connected to the 'u9' node with the type "nt0" and then returns the unique set of p2 property values for these nodes. The result returned by Neo4J is False, while Agensgraph returns False and None. This is because in Agensgraph, None indicates the absence, meaning that some nodes in the matched nodes may lack the p2 property, resulting in the presence of none. However, Distinct is meant to return unique elements, and after using distinct, None values should be removed to avoid potential user confusion.

@w158937299 w158937299 changed the title Bugdue to handling of None value Bug due to handling of None value Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant