Re: [Neo4j] Unique constraint and transaction over REST

Hey, Matt: This isn't related to this thread, but I noticed you are from Scholar.ly. I thought you might like this: http://arxiv.org/abs/0905.1594 Go Canucks!, Marko. http://markorodriguez.com On Dec 4, 2011, at 12:58 AM, Matt Luongo wrote: Well, I had already started writing this

Re: [Neo4j] Unique constraint and transaction over REST

Marko, Thanks for the link, it's obviously very relevant to what we're doing! We've talked a ton about trying to solve some of the problems it looks like k-reef was designed to, but weren't quite ambitious enough :) We have an alpha release coming up- would you be interested in seeing what we

Re: [Neo4j] Unique constraint and transaction over REST

I've run into this problem, and resorted to using the Gremlin/Groovy over REST (via the server-included plugin). There really isn't a way to transactionally express a conditional (or get-or-create) like that over the vanilla REST API, though I'm sure it's in the works. -- Matt Luongo Co-Founder,

Re: [Neo4j] Unique constraint and transaction over REST

Well, I had already started writing this before I saw your response- so, if you do decide down the road that you care more about immediate performance than keeping DRY... ;) g.setMaxBufferSize(0) //turn on tx handlings g.startTransaction() found =