-
Notifications
You must be signed in to change notification settings - Fork 193
1.0 changelog
Jacob Hansson edited this page Mar 21, 2016
·
14 revisions
###1.0.0rc2 ######Not yet released
###1.0.0rc1
- Session.del has been removed from the API. f1350ad
-
identity
methods renamedid
5ecd06d - Resolve bug in connecting to servers with authentication disabled. a67836a
###1.0.0b3
- Added support for encrypted connections with the server. Now the driver could communicate with the server in encrypted mode! Three encryption levels are added to choose from, a.k.a.
SECURITY_NONE
,SECURITY_TRUST_ON_FIRST_USE
andSECURITY_VERIFIED
[0a704b] (https://github.com/neo4j/neo4j-python-driver/commit/0a704b) - Along with encryption, authentication is also available! With authentication, it allows a driver to be created with authentication credentials which would be used by the server to log in the driver user. 95ff47
- A few method or property names in
ResultCurosr
get polished:
- Changed
summarize()
tosummary
9dc874 [034343] (https://github.com/neo4j/neo4j-python-driver/commit/034343) - Renamed
statistics
tocounters
3547dd - Changed
position()
toposition
[f505d6] (https://github.com/neo4j/neo4j-python-driver/commit/f505d6) - Changed
at_end()
toat_end
16c7e1
- Fixed a bug where the session might not be closed properly on calling
Session.__del__
###1.0.0b2
- ResultCursor#keys now works before the cursor has been moved. 92df09b
-
records
method is now calledstream
2793320 - Resolved an error in marking transaction as successful when using the context manager approach to transactions. 2793320
-
skip
,first
andsingl
methods have been removed. dce9cfe - New and more efficient ResultCursor API for statement results. b0faed3
- Sessions are now pooled for improved performance. 90397b4
- Fixed deserialization bug for Paths ec6d6d5
- Support for the latest draft version of the V1 Bolt Protocol 35d6911
- Include
neo4j.v1
package as installed package. 9e54fc3
###1.0.0b1
- First ever milestone! A fully new API for Neo4j, and a client implementation of the Bolt V1 protocol.