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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
