Re: [Neo4j] Unique constraint and transaction over REST

reate) like that over the vanilla REST API, though I'm sure it's in > the works. > > -- > Matt Luongo > Co-Founder, Scholr.ly > > > > On Thu, Dec 1, 2011 at 5:45 PM, dnagir <[hidden email]> wrote: > > > Hi, > > > >

Re: [Neo4j] Named matched with depth gives error

Neo4j Community Discussions] wrote: > download the 1.6 SNAPSHOT from neo4j.org/downloads > > mobile mail please excuse brevity and typos > > Am 02.12.2011 um 01:27 schrieb dnagir <[hidden email]>: > > >> I fixed this > >

Re: [Neo4j] Named matched with depth gives error

> I fixed this > yesterday. > Thanks a lot for that. How can I get the build that includes the fix? (Sorry for the question, but just starting with noe4j). > Sorry you ran into it... NP. Cheers. -- View thi

[Neo4j] Unique constraint and transaction over REST

Hi, I wonder what's the best way to do something similar to unique constraints in RDBMS. For example, user registration requires that the user's email to be unique. Working over in Ruby over REST API, how do you achieve this? I assume I need an auto-index on email property of User nodes. Then q

[Neo4j] Which Ruby REST client for neo4j?

Basically subject says it all. More detailed question is at SO: http://stackoverflow.com/questions/8335136/which-ruby-client-for-neo4j-rest-api So basically there are 3 main options: neograhy - just plain REST API. Nothing to do with models etc. neology - is just a wrapper over neography and isn'

[Neo4j] Named matched with depth gives error

Hi, I am trying this query: *START u=node(5963) MATCH p = (u)<-[r:selling*1..99]-() WHERE r.development=7867 RETURN p* But it gives the error: Error: *NoSuchElementException - key not found: r* When I remove the depth specification (*1..99) from the MATCH, it works as expected. What's a deal w

Re: [Neo4j] How to return the start nodes of all the paths with Cypher

On 30/11/2011, at 9:46 PM, Andres Taylor [via Neo4j Community Discussions] wrote: > Well, this query would also return 'b' in the example you shared above. You're right. Too late here already. Can't think clearly. > I think we need something that says "follow this path until you can't follow

Re: [Neo4j] RETURN DISTINCT with ORDER BY

Thanks. This does work indeed. Much like in SQL :) On 30/11/2011, at 6:37 PM, readic [via Neo4j Community Discussions] wrote: > try this: > start d=node(17) match d-[*0..99]->x return distinct x,x.name order by x.name > > If you reply to this email, your message will be added to the discuss

Re: [Neo4j] How to return the start nodes of all the paths with Cypher

I would probably like to write something among these lines (it's not valid query of course): START s=node(10) MATCH p = s<-[:whatever]-t RETURN t, LENGTH(p) as len HAVING len >= MAX( LENGTH(p) ) Seems like clause similar to SQL HAVING is missing. It doesn't "exactly" reflect what I want but jus

[Neo4j] How to return the start nodes of all the paths with Cypher

Hi, How can I find all the nodes that "start a path" So that I start at node "c" and paths "a->b->c", "d->c", "d->b->c", "e->f->c" I want to retrieve nodes "a", "d" and "e". -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/How-to-return-the-start-nod

[Neo4j] RETURN DISTINCT with ORDER BY

Hi, I wonder how can I use both distinct and order by in the queries. These 2 work as expected: start d=node(17) match d-[*0..99]->x return x order by x.name start d=node(17) match d-[*0..99]->x return distinct x But the query with both DISTINCT and ORDER BY doesn't return anything: start d=