Skip to content

Detection of cycles too defensive #2317

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

Closed
meistermeier opened this issue Jul 7, 2021 · 0 comments
Closed

Detection of cycles too defensive #2317

meistermeier opened this issue Jul 7, 2021 · 0 comments
Assignees

Comments

@meistermeier
Copy link
Collaborator

With a graph like this
image
the internal logic will determine C->D as an indicator for a cycle.
It gets processed twice by A->B->C->D and A->C->D

This should be a "directed" query instead of the data-driven one for cycles.
BUT I don't know yet if it makes sense because with a "directed" query, we would duplicate all the nodes and relationships behind the D in two separated branches starting from A.

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