Hi Faruk, We're already working on providing pattern matching in 2.2. We are already satisfied with what is already working, but it's too early for the show time. I can just say it's not Cypher but something that is well integrated with the rest of OrientDB SQL, but still declarative.
Best Regards, Founder & CEO OrientDB <http://orientdb.com/> On 15 July 2015 at 23:37, Işık Faruk S. Can <[email protected]> wrote: > Hi everyone, > > Seeing post very late but my points are; > > A declarative pattern matching language should be used for graph db > querying not a language that is designed to query DBMS that is not capable > of modelling graph data. The deficiency and inconvenience of such systems > in modelling graph data is reflected by the language that is designed to > query them, the SQL. It is even very messy to query the DBMSs it is > designed for querying. > > No offence but any extensions to it just makes it more crowded. Having > such a good graph data modelling capability with performance and permissive > licence and having SQL to query it? SQL, it is just not for it. > > Thanks. > > On Saturday, April 27, 2013 at 9:19:35 PM UTC+3, Tomas Bosak wrote: >> >> Hi folks, >> >> have you guys investigated/evaluated/thought about the usage of cypher >> language [1] for querying in orient? >> >> [1]: http://docs.neo4j.org/chunked/stable/cypher-query-lang.html >> > -- > > --- > 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.
