MironAtHome closed issue #1629: OPTIONAL MATCH should act as outer
relationship, acts as cross join
URL: https://github.com/apache/age/issues/1629
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
MironAtHome commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-2016457852
Used Neo4J [sandbox](https://sandbox.neo4j.com/) to verify my report above.
Looks like Neo4J behaves identically to Age.
Closing this bug / question.
--
This is an automated
MironAtHome commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-1977018339
I think it is not really question of match, but a question of what
"optional" means.
Based on what I have gathered from the documentation ( provided in the
comments ) optional
jrgemignani commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-1971936626
@MironAtHome If this resolves your question, please consider closing the
ticket :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please
jrgemignani commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-1971933158
@MironAtHome I think your misunderstanding with **OPTIONAL MATCH** is with
how **MATCH** works with **patterns**. **OPTIONAL** **MATCH** and **MATCH**
process **patterns** in the
MironAtHome commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-1970556683
Reproduced on both, Windows and Linux.
Workaround, produces left outer join:
```
SELECT * FROM cypher(
'test_graph'
, $$
MATCH (a:vertice1)
OPTIONAL MATCH
MironAtHome opened a new issue, #1629:
URL: https://github.com/apache/age/issues/1629
**Describe the bug**
Statement below does not return rows, should return
LOAD 'age';
SET search_path TO ag_catalog;
SELECT create_graph('test_graph');
-- SELECT drop_label('test_graph',
