Heinrich Klobuczek

@am17torres I totally agree with you. What you intend to do should be possible. Having said that I cannot imagine we will have the time to address that before we...

@yourpalal strictly speaking you don't need to add specs for equivalent backwards compatible code refactoring. However it looks like you are trying to overcome a bug here. The gem cannot...

@yourpalal I am just thinking.. maybe another solution could be ignoring all records without id_property. @amitsuryavanshi thoughts?

@yourpalal a word of advise: if you created a PR without all the renaming and reformating, just fixing the problem with the least character changes your PR would've been merged...

@yourpalal really sorry for taking that long to review this. Could you merge master to your branch and add a spec that fails on master but passes on your branch....

Hi @subvertallchris, our team has taken over the maintenance of neo4jrb. I'm not sure what the plan with the neo4j.io site should be. It has not been maintained for a...

Further insights. Even this simpler case exposes what I believe, after some analysis, is the same bug as above and fixing the below will fix as well the above. ```...

@mstrofbass have you tried to set the config value: ``` keep_alive: true ``` This instructs the neo4j server to send periodic NO_OP messages (not sure how often) to the client...

@efivash @mperice let's move the discussion to https://github.com/neo4jrb/neo4j-ruby-driver/pull/47

@am17torres as far as I can tell this was not intended as part of the public API but if you look through the code I am sure you can find...