[Neo4j] Using bound identifiers in MATCH statements fails as of 2.1 Cannot match on a pattern containing only already bound identifiers

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

Re: [Neo4j] Using bound identifiers in MATCH statements fails as of 2.1 Cannot match on a pattern containing only already bound identifiers

) 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

Re: [Neo4j] Optional match property updates don't work together

creative party in Malmö - Kidscraft ICE http://kidscraft.se On Mon, Jan 27, 2014 at 4:40 PM, Jon Packer con...@jonpacker.comjavascript: wrote: Hi! I'm trying to do some property updates with an OPTIONAL MATCH, and having a bit of trouble. It's OK when the OPTIONAL MATCH's pattern matches

[Neo4j] Optional match property updates don't work together

Hi! I'm trying to do some property updates with an OPTIONAL MATCH, and having a bit of trouble. It's OK when the OPTIONAL MATCH's pattern matches something, but when it doesn't, I get a ThisShouldNotHappenError with the message Developer: Stefan claims that: This should be a node or a