Mmh, not sure what the expected behavior is. I agree that it looks like it should follow the underlying Neo4j conventions. Could you file a bug on that so Tobias can comment on it?
Cheers, /peter neubauer COO and Sales, Neo Technology GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Sun, Aug 1, 2010 at 4:47 PM, Thomas Fenzl <[email protected]> wrote: > Hi all, > > I'm writing some learning tests to understand the python bindings to > neo4j. The code can be found at bitbucket ( > https://bitbucket.org/another_thomas/learnneo4jpy) if anyone is interested. > Still working on basic stuff, I found a difference between the behavior > of neo4j-python and neo4j as described in the Java API. > > I did not expect the following to work: > >>with graph.transaction as tx: >> id = graph.node(name="foo").id >>with graph.transaction as tx: >> print graph.node[id] > > as according the Java API, transactions should roll back unless > explicitly marked successful. > Neo4j-python used was head from svn, using jpype. > > Is that different behavior on purpose? > > Thanks, > Thomas > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
