neo4j-driver-go-skill

To execute queries safely with the Neo4j Go driver, use `neo4j.ExecuteQuery` as the recommended default API with parameterized Cypher inputs. This approach handles managed transaction streaming for large results and ensures safe Go↔Cypher data type mapping without fragile boilerplate.

Use `neo4j.ExecuteQuery` for standard query execution, but switch to explicit transactions via `BeginTransaction` when you need multi-step coordination. Managed transactions (`ExecuteRead`/`ExecuteWrite`) are preferred for handling large result streaming in the Neo4j Go driver.

Handle Neo4j Go driver errors by distinguishing `Neo4jError` from `ConnectivityError`. Ensure safe Go↔Cypher type mapping by extracting record values without unsafe assertions, properly managing null values to prevent subtle production bugs.

Initialize the Neo4j Go driver for production by creating one goroutine-safe driver instance per application using `neo4j.NewDriver`. Call `driver.VerifyConnectivity` at service startup, specify the database explicitly, and propagate `context` with timeouts.

Manage causal consistency in the Neo4j Go driver by maintaining bookmark awareness across transactions. This ensures read-after-write consistency by routing subsequent read queries to the correct cluster member using session bookmarks.

Perform batch writes in the Neo4j Go driver by using parameterized Cypher queries with `UNWIND`. This allows efficient bulk data ingestion by passing large parameter arrays to `neo4j.ExecuteQuery`, ensuring safe type mapping and robust error handling.