Releases: neo4j/neo4j-jdbc
Release 3.5.1
New Release 3.5.1
Mostly upgrades and bugfixes, no big new features.
- bump to Neo4j v 3.5
- fixed getIndexInfo in v 3.5
- bump java driver version to v 1.7.5
- added readonly=true/false parameter to URL to make all connections read-only (for routing only!)
- resolved jackson databind CVE update
- Remove unsupported operation exception from driver, resultset, statement and connection (#199)
- Improve/Optimize the Driver management in pool (#178)
- Neo4jDatabaseMetaData#getIndexInfo should return the indexes of the label #198
- fixes #187: Make all DatabaseMetaData methods more lenient and not throw exceptions. (#192)
- fixes #187: Intellj Datasource browser Method supportsSavepoints in class org.neo4j.jdbc.Neo4jDatabaseMetaData is not yet implemented.
- Issue 188: Why neo4j-jdbc-http driver request two times - pre-emptive auth request (#191)
- fixes #179: BoltRoutingNeo4jDriver - Issue with Boolean Data type (#190)
Neo4j JDBC Release 3.4.0
The release has been upgraded to work with recent Neo4j 3.4.x versions and bolt-driver 1.6.1.
We worked on a number of improvements:
-
Added support for date, time and spatial datatypes for Neo4j 3.4
-
Upgraded to Neo4j Java driver 1.6.1
-
Added BOLT+ROUTING protocol to let the driver work with the cluster and being able to route transactions to available cluster members.
-
Added support for bookmarks, readonly transactions, routing policies and routing servers
-
Added support for in-memory databases for testing and embedded use-cases.
-
Added a debug feature to better support the development phase or inspect how the driver works when used by third-party tools.
-
Added support for TrustStrategy so that you can now configure how the driver determines if it can trust the encryption certificates provided by the Neo4j instance it is connected to.
-
Implemented the DataSource interface so that you can now register the driver with a naming service based on the Java Naming and Directory (JNDI) API and get a connection via JNDI lookups.
-
Allow additional bolt driver configuration via properties or URL parameters
PLEASE NOTE: we’ve deprecated the usage of “,” as the parameter separator in favour of “&” to be compliant with the URL parameter syntax. Please update your connection URL as in future releases we’ll manage just “&” (we want to use “,” for parameters that can have list of values).
We added a new Matlab example. Besides that, Neo4j-JDBC can of course be used with many other tools.
Here is a short list:
- Squirrel SQL
- Eclipse / BIRT
- Jasper Reports
- RapidMiner Studio
- Pentaho Kettle
- Streamsets
We really hope you enjoyed our work and we'd love to hear from you, not just about issues but also how you use the JDBC driver in your projects or which tools that we have not yet mentioned work well with it.
If you want to use the neo4j-jdbc driver in your application, you can depend on org.neo4j:neo4j-jdcb:3.4.0 in your build setup, while for use with standalone tools it's best to grab the full release JAR here from GitHub.
Neo4j-JDBC Release 3.3.1
The release has been upgraded to work with recent Neo4j 3.3.x versions and bolt-driver 1.4.6
(work on Neo4j 3.4.x and drivers 1.6.x is in progress).
We worked on a number of improvements:
- Added BOLT+ROUTING protocol to let the driver work with the cluster and being able to route transactions to available cluster members.
- Added support for bookmarks, readonly transactions, routing policies and routing servers
- Added support for in-memory databases for testing and embedded use-cases.
- Added a debug feature to better support the development phase or inspect how the driver works when used by third-party tools.
- Added support for TrustStrategy so that you can now configure how the driver determines if it can trust the encryption certificates provided by the Neo4j instance it is connected to.
- Implemented the DataSource interface so that you can now register the driver with a naming service based on the Java Naming and Directory (JNDI) API and get a connection via JNDI lookups.
PLEASE NOTE: we’ve deprecated the usage of “,” as the parameter separator in favour of “&” to be compliant with the URL parameter syntax. Please update your connection URL as in future releases we’ll manage just “&” (we want to use “,” for parameters that can have list of values).
We added a new Matlab example. Besides that, Neo4j-JDBC can of course be used with many other tools.
Here is a short list:
- Squirrel SQL
- Eclipse / BIRT
- Jasper Reports
- RapidMiner Studio
- Pentaho Kettle
- Streamsets
We really hope you enjoyed our work and we'd love to hear from you, not just about issues but also how you use the JDBC driver in your projects or which tools that we have not yet mentioned work well with it.
If you want to use the neo4j-jdbc driver in your application, you can depend on org.neo4j:neo4j-jdcb:3.3.1 in your build setup, while for use with standalone tools it's best to grab the full release JAR here from GitHub.
Neo4j JDBC Release 3.3.0
After a while we're happy to announce the 3.3.0 release of the neo4j-jdbc driver.
The release is upgraded to work with Neo4j 3.3.0 and recent bolt-drivers.
- Added a debug feature.
- Added support for TrustStrategy.
We added support for in-memory databases for testing and embedded use-case.
We updated the documentation to include matlab and the new features.
- We implemented DataSource.
- Added implementations for several methods in Driver, Connection, Statement, ResultSet that were not yet implemented.
Thanks a lot to @glaggia-larus from our partner Larus IT in Italy for all the work.
Neo4j JDBC Release 3.1.0
First release for Neo4j 3.1.x
Contains the following fixes:
- Update to Neo4j 3.1.4, neo4j-java-driver 1.3.0, http-client 4.5.3, jackson 2.8.8
- Only shade the neo4j-jdbc-driver project and the other (#91)
- Correct bug that switch to non-autocommit mode when there is an error
- Improvement on BoltDatabaseMetaData + aligned BoltStatement.execute with BoltPreparedStatement.execute
- BoltDatabaseMetadata.getTables implementation returning Labels list. Fixes Issue #85
- Mybatis example added
- fFx int and float conversion to string
- ResultSet.getInt/Long/Float/Double now return 0 for NULL values, getBoolean returns false for NULL values. Fixes issue #81
Neo4j JDBC Release 3.0.3
Release for Neo4j 3.0.x
Contains the following fixes:
- Update to Neo4j 3.0.9, neo4j-java-driver 1.3.0, http-client 4.5.3, jackson 2.8.8
- Only shade the neo4j-jdbc-driver project and the other (#91)
- Correct bug that switch to non-autocommit mode when there is an error
- Improvement on BoltDatabaseMetaData + aligned BoltStatement.execute with BoltPreparedStatement.execute
- BoltDatabaseMetadata.getTables implementation returning Labels list. Fixes Issue #85
- Mybatis example added
- fFx int and float conversion to string
- ResultSet.getInt/Long/Float/Double now return 0 for NULL values, getBoolean returns false for NULL values. Fixes issue #81
Release 3.0.2
- issues on mybatis integration solved
- #85 resolution
- minor improvement on BoltDatabaseMetadata
3.1-SNAPSHOT
3.1-SNAPSHOT (i.e. not a release indeed) just meant to facilitate the distribution of binaries to end users.
Bug fixed:
Release 3.0.1
This release includes:
- neo4j-java-driver 1.0.5 update
- BoltConnection.isValid(int) implementation
- Connection.setTransactionIsolation(int) default implementation
- DatabaseMetadata.getDefaultTransactionIsolation returns Connection.TRANSACTION_READ_COMMITTED
- Connection.prepareStatement(String sql, int autoGeneratedKeys) default implementation
- ResultSet.getFetchSize() default implementation
- ResultSet.setFetchSize(int) default implementation
and fixes the following issues:
Neo4j JDBC 3.0 Release
First GA release of the 3.0 Neo4j-JDBC driver.
- Extensive Tests with a variety of tools
- Bug Fixes
- Documentation
- Better handling of credentials
- Support for additional API methods
- Explicit enabling of flatten= via jdbc URL