Hi Riccardo, We mainly added it because solving some use cases is sometimes very tricky with SELECT and TRAVERSE only. One example is this one
https://github.com/orientechnologies/orientdb-docs/blob/master/SQL-Match.md#real-use-case-manager-in-an-incomplete-hierarchy Try to write a SELECT/TRAVERSE query to solve it and you'll see it's not trivial ;-) Thanks Luigi 2016-02-23 11:23 GMT+01:00 Riccardo Tasso <[email protected]>: > 2016-02-23 0:01 GMT+01:00 Luca Garulli <[email protected]>: > >> - New Pattern matching > > > This is very interesting, it reminds to me both the SPARQL query language > and the Match Step in Gremlin ( > http://tinkerpop.apache.org/docs/3.1.1-incubating/reference/#match-step). > > Have you decided to add it to provide some kind of interoperability > between Orient and those languages or there was some real use case that > required this command? > > I can't figure out a scenario where Pattern matching would result better > (with any criterion) than OSQL: what's your opinion? > > Cheers, > Riccardo > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
