Thanks for the suggestion Dmitry. I was hoping for a solution which didn't involve changing the configuration or the query.
On Monday, 22 December 2014 09:56:11 UTC+5:30, Dmitry Davletbaev wrote: > > Hello Ducky! > > You can edit a cypher_parser_version option in ./conf/neo4j.properties to > force Neo4j to use specific Cypher version parser, e.g.: > > # Enable this to specify a parser other than the default one. > cypher_parser_version=2.0 > > I hope this helps you. > > Dmitry Davletbaev > Software Developer > dmitry.d...@maginfo.com <javascript:> > http://www.maginfo.com/ > > On Sunday, December 21, 2014 2:36:01 PM UTC+5, ducky wrote: >> >> While testing some code against Neo4j 2.2M02, I realised that cypher >> queries of type "START n=node(1) RETURN n" are all breaking with error: >> >> Using 'START x = node(1)' is no longer supported. Please instead use 'MATCH >> x WHERE id(x) = 1' (line 1, column 7) "START x = node(1) RETURN x;" >> >> Neo.ClientError.Statement.InvalidSyntax >> >> >> >> This is a big breaking change. I understand that I can prepend the query >> with "CYPHER 2.1" to get the old behaviour. >> >> I remember talking to Chris Leishman about it at Neo4j GraphDay and he >> suggested that the 2.2 query engine would fallback to 2.1 engine if it >> encounters queries which it can't parse but would parse in 2.1 engine. >> >> Is that fallback still on cards? >> >> cheers >> > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
