Dieter Pisarewski

It can use `NODES(path)` to get all nodes from the path. I'm curious if it's better to implement a `Path` class which could return nodes or relationships.

@subvertallchris, @cheerfulstoic Yes, I would expect methods like `node`, `rels` which return nodes and relationships, and `each` method which will iterate over nodes and relationships together, so I would get...

Well, I expect that by calling `Neo4j::Transaction.current` I won't get an expired transaction. It could also update the value of 'expires' since neo4j rest api always returns it. http://neo4j.com/docs/stable/rest-api-transactional.html#rest-api-execute-statements-in-an-open-transaction-in-rest-format-for-the-return

I agree that all requests inside an invalid transaction must fail. But when you already know the transaction is invalid then you don't need to send requests to the database....

No, I think `Neo4j::Transaction.current` should be nil as there is no valid transaction. And I should be able to create a new transaction and get this transaction by calling `Neo4j::Transaction.current`....

Maybe I'm wrong and neo4j-core should not be responsible for removing expired transactions.

That sounds good.

Here is it. https://github.com/neo4jrb/neo4j-core/pull/156

Oh sorry, there are merge conflicts.

I added some examples into cypher_transaction_spec.rb. Why is the whole spec commented out? https://github.com/neo4jrb/neo4j-core/blob/master/spec/neo4j-server/unit/cypher_transaction_spec.rb