I'm still in designing phase of my system so I have no specific situations yet.
I think that transactions would be required for me to do the following as 1 atomic operation: - create a (few) new nodes - link the nodes into the graph - add indices - change some other node properties If at any point one operation fails it should cancel all the others (like ACID transactions in simple neo4j do). Or can this be done as a bulk upload? If so, how can cancelling be done? MikKi > Hey MikKi, > > Could you elaborate a bit more on your use case? If you want transaction > control then perhaps it's widespread enough that other folks would want it > too. > > Jim > > > On 2 Nov 2010, at 09:16, Kiss Miklós wrote: > >> Hi Jim, >> >> Yes, I mean controlling transaction lifecycle. Support for bulk >> uploading won't fit all my needs. >> I guess I'll have to write my own DB server for my own needs. >> >> MikKi >> >> 2010.10.29. 17:35 keltezéssel, Jim Webber írta: >>> Hi MikKi, >>> >>> Transactions are everywhere in Neo4j, in fact each time you use the REST >>> API a transaction wraps the work on the underlying graph store. >>> >>> I suspect you're wanting to control transaction lifecycle so that you can >>> do bulk inserts for example? >>> >>> I have to say I'm not keen at all on exposing transactions outside the >>> server, they're a database thing not a network thing (influenced by Pat >>> Helland's work: http://msdn.microsoft.com/en-us/library/ms954587.aspx). >>> However I would like to see the ability to do bulk uploads and I want to >>> design that into the REST API in the future. >>> >>> I don't have any timescales around this specifically, but I am now a full >>> time committer to Neo4j and I'm focussing my efforts on creating a server >>> product that fulfils these kind of ambitions (since I share them), and >>> other more mundane, but critically important, aspects like alerting, >>> monitoring, etc. >>> >>> However, in the short term (hopefully in the current snapshot release due >>> out in a week) there'll be the option to register your own code at a URI on >>> the server. If you can't wait for me to get on to it, then in the meantime >>> you should easily be able to write your own bulk uploader and host it on >>> the Neo Server. >>> >>> Jim >>> _______________________________________________ >>> Neo4j mailing list >>> User@lists.neo4j.org >>> https://lists.neo4j.org/mailman/listinfo/user >>> >>> >> _______________________________________________ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
