-
Notifications
You must be signed in to change notification settings - Fork 408
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
feat: Implement OPTIONAL MATCH
#175
Conversation
There are some minor formatting (coding standard) issues that need to be addressed. Additionally, I would like to see some more commenting of functions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coding is good! You just need to make sure that the code conforms to AGE's coding standard which changed from PG and AgensGraph.
Also, please add in a bit more comments into the code.
…onal_match_rebase # Conflicts: # src/backend/parser/cypher_clause.c
Please resolve the conflicts listed above. |
# Conflicts: # src/backend/parser/cypher_gram.y
Wait... |
Fixed. |
* feat: Implement `OPTIONAL MATCH` * Reflect review. * Reflect review * Reflect review * Reflect review * Reflect review * Reflect Review * Reflect review * Reflect review * Fix broken
This implements the
OPTIONAL MATCH
clause. Internally, it is implemented usingLEFT JOIN LATERAL
of PostgreSQL.Apart from the
OPTIONAL MATCH
implementation, it also includes code that solves the problem ofORDER BY
Clause.Previous PR : #149
Jira : https://issues.apache.org/jira/projects/AGE2/issues/AGE2-508