-
Notifications
You must be signed in to change notification settings - Fork 70
1.7 changelog
Ali Ince edited this page Aug 23, 2018
·
17 revisions
- Removed
master
branch and made1.7
the default which will hold the long run stable 1.7 driver release (the same applies to downstream -gobolt
andseabolt
). - Renamed seabolt wrapper from
neo4j-go-connector
togobolt
(accessible at https://github.com/neo4j-drivers/gobolt) - Changed the package structure of the driver as per packaging guidelines and moved top level code into
neo4j
folder which can now be imported fromgithub.com/neo4j/neo4j-go-driver/neo4j
- Made the logger provided to the driver through
neo4j.Config
to be used across the whole stack (now you can get more useful log entries fromseabolt
- especially whenDEBUG
log level is enabled) - Added support for
bolt+routing
scheme to work against causal cluster deployments, yay! (all you need to do is to point your URL tobolt+routing://<hostname>:<port>
where<hostname>:<port>
pair points to one of the core servers in the cluster) - Added support for specifying custom
neo4j.ServerAddressResolver
throughneo4j.Config
that can map<hostname>:<port>
pair provided as part of the driver URL to multiple entries (i.e to provide all core server addresses) - so that all those mapped entries are tried in turn until routing table is fetched - Renamed spatial type constructor function
neo4j.NewPoint
toneo4j.NewPoint2D
for consistency - Enabled SNI extension on TLS sessions
- Added support for all temporal and spatial types that were introduced by Bolt version 2 (introduced as part of server release 3.4)
- Added support for returning Path types as return values
- Fixed an issue where node and relationship values returned from a query was not accessible through driver
- The first release of the Neo4j Official Go Driver. It only includes support for Bolt V1 (which means you cannot use temporal / spatial types introduced with Neo4j database 3.4 version) and works only on direct mode (no clustering support)