Chris Collison

I haven't started down this path yet but I did notice neo4j just released an official go driver and had a temporal implementation in it: https://github.com/neo4j/neo4j-go-driver/blob/1.7/neo4j/values_temporal.go

I've started to test it out, it appears to be functionally sound but because it's a wrapper around [seabolt](https://github.com/neo4j-drivers/seabolt) it comes with the headache of managing a C toolchain which...

Our scenario is quite different. We're ingesting messages off a message broker and using a persistent connection pool to send a merge to our Neo4j instance. Our Neo4j instance is...

After digging into this more it appears that connections do become stale after a sufficient idle period. I came up with a couple of different ideas how to deal with...

Yeah, this doesn't seem to fix the issue in our environment either. Believe it's a sync/cross-threading issue, I've been able to reproduce this issue with this simple POC: https://github.com/collisonchris/neo4j-test The...

Yeah this looks like a type of unintended concurrent access of the underlying Conns; multiple go routines are hitting the same connection and execute queries in an interleaved fashion. The...

Looks like a much more robust way of resetting connections when they go idle.

Yikes. I didn't even notice the license difference. Agree on the 3rd option being the easiest.

Not sure if you're trying to do the same thing I am but I used this method to share conn objects/embed the `DriverPool` ``` type NeoClient struct { Pool bolt.DriverPool...

I've run into this a few times and carefully looking at how I was setting up the execution lead me to follow the same path @sh0umik did, closing the statment...