On Tue, Jun 28, 2011 at 1:27 PM, Adrian Stabiszewski < [email protected]> wrote:
> Thanks for your answers. The correct quotation marks are working. Couldn't > find this in the docs. > It's under the return statement. I'll make it clearer. Thanks for the pointer. > > It is not possible now. It is however something that we want to have. > We're > > closing in on the next stable release, and variable length connections > are > not > > going to make it into 1.4. It should be available soon after though, if > nothing > > shakes the plan as we now know it. > > This would be great. Will it also be possible to retrieve the path? Say all > nodes between c and e? I'm asking because since I don't know how may > relationships are between the nodes, it is not possible to give them > identifiers. Well, it's not clear how we will solve it. But yes, we have to make it possible to return and query on the content of the path. > There are reasons why we have chosen not to expose things like index > > queries > > in the MATCH and WHERE statement. What is it that you are trying to do? > > Maybe I can help you figure out a better way of doing it? > > Basically I thought I could improve performance in the WHERE statement if I > could use indices there. Something like in the START statement. > Cypher is a declarative language. That means we try to make it so that you don't have to think about how to access the data - just which data you would like. With the addition of auto indexing in 1.4, Cypher will be able to see what indexes are available, and how to construct the execution plan as efficiently as possible. So if you have an index on the node type, and an index on the name, Cypher will be able to figure out that a lucene index join is the best way to do this query. Regards, Andrés _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
