Not even then, only for legacy indexes.
for the ID you can use MATCH (n) WHERE id(n) = {id} RETURN n
Michael
Am 30.04.2014 um 02:35 schrieb Alex Frieden <[email protected]>:
> Start is definitely useful when you know the Id and want to anchor your
> query.
>
> On Apr 29, 2014 7:25 PM, "Spencer Kohan" <[email protected]> wrote:
> Using Neo4j 2.0.2 on JDK 8.1, OSX 10.9.2
>
> So I've been working my way through the manual, and I'm a little unsure what
> the best practice is regarding START and MATCH. It seems like almost any
> query using a START clause has an equivalent using MATCH ... WHERE, and this
> note in the docs seem to hint at the fact that START is no longer the best
> practice for queries:
>
> Note
> START is optional. If you do not specify explicit starting points, Cypher
> will try and infer starting points from your query. This is done based on
> node labels and predicates contained in your query. See Chapter 13, Schema
> for more information. In general, the START clause is only really needed when
> using legacy indexes.
>
> So I'm wondering, is START still considered best practice for some use cases?
> Are there performance differences between queries using START and queries
> using MATCH ... WHERE?
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
