That's great news! Our codebase relies pretty heavily on the MATCH 
(user:user) syntax, so I will most likely just hold out at 2.1.3 until the 
next version comes along. 

Thanks for the help Michael :)

On Monday, 23 June 2014 13:15:21 UTC+2, Michael Hunger wrote:
>
> Hi John,
>
> sorry this has been a well-intended change in 2.1.2 that was added to 
> protect people from using a node with two different labels resulting in 
> zero results.
>
> Unfortunately it has many not so good side-effects. So we'll probably roll 
> it back in the next version.
>
> Until then please use:
>
> START user = node(5)
> WHERE user:user
> RETURN user
>
>
> Am 23.06.2014 um 13:01 schrieb Jon Packer <con...@jonpacker.com 
> <javascript:>>:
>
> Hi there!
>
> I'm having this problem in the versions above 2.1. It's no longer possible 
> to use the START clause in conjunction with labels—using labels to enforce 
> the type of the node.
>
> For example, this:
>
> START user = node(5)
> MATCH (user:user)
> RETURN user
>
> now fails with "Cannot match on a pattern containing only already bound 
> identifiers". The purpose of this query would be to enforce that node(5) 
> is of type :user.  
>
> Is this a bug, or intended? If it is intended, is there any way to reform 
> this query to do the same thing in a 2.1 compatible way? Using MATCH to do 
> it would be preferable, as my use case (seraph-model 
> <https://github.com/brikteknologier/seraph-model>) sometimes allows for 
> properties to be added to the MATCH statement.
>
> Beyond that, it just seems like a strange restriction to have. While the 
> following might be a silly query, I see no clear reason why it should fail 
> and spit out an error. To the uninitiated this would seem like a perfectly 
> valid query.
>
> MATCH (user { name: 'Johanna Kurkela' })
> MATCH (user:user) 
> RETURN user
>
> >> Cannot match on a pattern containing only already bound identifiers 
> (line 2, column 1)
> "MATCH (user:user) "
>
> -- 
> 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+un...@googlegroups.com <javascript:>.
> 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 neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to