I made one of the classic presentation errors by not repeating and summarizing comments and questions from the audience for the microphone.
First person asked why it was Neo4j::Transaction.new ; #... ; Neo4j::Transaction.finish instead of Neo4j::Transaction.new do ... end. The answer was that that form is also available. Another person mentioned that these were some sort of native Java transaction.
Another person asked if you could use this to handle graph problems while using Couch or another database for storage. I said "maybe" and another person offered that it seemed to them like it would probably be ok to do all your storage in Neo4j.
Someone brought up how this type of thing could solve some Project Euler problems like we'd seen at a previous meeting. It totally could.
Next question was "is there a large Ruby community around this?": No. :)
Post Comments
Add Your Comment!
Log in to leave a comment or Create an accountsamsm writes:
I made one of the classic presentation errors by not repeating and summarizing comments and questions from the audience for the microphone.
First person asked why it was Neo4j::Transaction.new ; #... ; Neo4j::Transaction.finish instead of Neo4j::Transaction.new do ... end. The answer was that that form is also available. Another person mentioned that these were some sort of native Java transaction.
Another person asked if you could use this to handle graph problems while using Couch or another database for storage. I said "maybe" and another person offered that it seemed to them like it would probably be ok to do all your storage in Neo4j.
Someone brought up how this type of thing could solve some Project Euler problems like we'd seen at a previous meeting. It totally could.
Next question was "is there a large Ruby community around this?": No. :)
» Comments RSS