Releases: neo4j/neo4j-dotnet-driver
1.3.0-rc1
1.2.1
1.3.0-beta01
The 1.3 series is coming! This first release includes a few new enhancements to the routing driver such as accepting routing context from the routing uri. It also includes a few 1.2 bug fixes such as fixing connection errors on some operation systems.
See more details at our changelog.
1.2.0
We would like to present the 1.2 driver which provides improved Causal Clustering API. The improved API which
- automates the passing of causal consistency context (bookmark) within Sessions
- prevents Driver death when the database service is completely unavailable
- hides failures that are caused by cluster leader switch by replay transactions using the strategy defined by retry logic
Checkout driver documentation for more information of how to use the new API.
1.2.0-beta01
The first release of the new 1.2 driver!
1.1.2
1.1.1
1.1.0
We would like to represent you the new 1.1 routing driver which adds routing and simple load balancing. This means that with the routing driver, the application user/operator does not need to add logic to their application or additional components to their infrastructure to interact with a Neo4j 3.1+ Causal Cluster. To use the new routing driver, just specify bolt+routing as the scheme in the URL when connecting to the cluster.
Read the changelog for more information about this release!