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

New TRAVERSE operator taken by GraphDB [moved] #24

Closed
lvca opened this issue Dec 10, 2012 · 1 comment
Closed

New TRAVERSE operator taken by GraphDB [moved] #24

lvca opened this issue Dec 10, 2012 · 1 comment
Assignees

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 24 moved from a Google Code project.
Added by 2010-04-20T09:06:22.000Z by [email protected].
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-High, graph, query, sql

Original description

Orient is a document-graph DBMS. It should be straightforward to implement
a TRAVERSE operator to go in deep in the graph and checking the condition
against all the node. Example:

(1) Find all the people that descend by 'Adam':

select from person where parents TRAVERSE (name="Adam")

(2) Find all the people that have Luca Garulli as relationship in any order:

select from person where ANY(parents,children) TRAVERSE (name="Luca" and
surname="Garulli")

or to search in any fields:

select from person where ANY() TRAVERSE (name="Luca" and surname="Garulli")
@lvca
Copy link
Member Author

lvca commented Apr 24, 2013

We already have it since long time.

@lvca lvca closed this as completed Apr 24, 2013
@ghost ghost assigned lvca Apr 24, 2013
lvca added a commit that referenced this issue Oct 15, 2015
lvca added a commit that referenced this issue Oct 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant