[Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread noppanit
Basically, I'm trying to implement rules engine in neo4j and I think that pattern matching would be the right way to find the rule. But I really don't know how to do that in Cypher or even in PatternMatching. This is my graph (customers)---[:applies]--(rules)

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread Andres Taylor
Hi there, Your images are difficult to read on gmail. A gif might help. :) I'm not quite certain on what is not working. In Cypher, your question would look something like this: START rules=(0) MATCH (subReference )-[:APPLIES]-(rules)-[:RULE]-(rule)-[r,:LESS_THAN]-(answer) WHERE r.Threshhold 0

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread noppanit
Thanks for the reply, sorry the DatabaseHelper is just my class to get an index of a node. :) Will try that soon, Thanks very much. -- View this message in context: http://neo4j-user-list.438527.n3.nabble.com/I-m-really-stuck-in-PatternMatching-tp3072170p3072365.html Sent from the Neo4J User

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread noppanit
From the query above I got this error. org.neo4j.cypher.SyntaxError: string matching regex `(?i)\Qreturn\E' expected but ` ' found What does it mean? Thanks :) -- View this message in context:

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread noppanit
Hi!, I've fixed that issue already, it's because I forgot to load my database up. But now I got a new error from ExecutionResult Method threw 'java.lang.UnsupportedOperationException' exception instead when I debug it. -- View this message in context:

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread noppanit
Hi, I found the error already, but I'm not sure if it's related to the API. If I use AND in the WHERE clause. It causes the error, but If I use and it runs ok. :) -- View this message in context:

Re: [Neo4j] I'm really stuck in PatternMatching

2011-06-16 Thread Andres Taylor
On Thu, Jun 16, 2011 at 6:22 PM, noppanit noppani...@gmail.com wrote: Hi, I found the error already, but I'm not sure if it's related to the API. If I use AND in the WHERE clause. It causes the error, but If I use and it runs ok. :) Good catch. Fixed in trunk now. Andrés