You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* renamed readme and removed aio.rst
* changed theme to read the docs
* changed readme to be markdown
* updated the index to include breaking changes
* updated breaking changes about renaming
* Updated docs
* the docs is building ok now.
* added more patterns
* improved index
Renamed the headline to be Neo4j Python Driver
Added the Bolt Protocol Version information for the supported Neo4j
versions.
* added link to migration guide on index page
The Official Neo4j Driver for Python supports Neo4j 3.2 and above and requires Python version 2.7 or 3.4+.
6
-
Note that support for Python 2.7 will be removed in the 2.0 driver.
5
+
.. warning::
6
+
This API docs is not production ready!
7
7
8
8
9
+
The Official Neo4j Driver for Python.
10
+
11
+
Neo4j versions supported:
12
+
13
+
* Neo4j 4.0 - Using the Bolt Protocol Version 4.0
14
+
* Neo4j 3.5 - Using the Bolt Protocol Version 3
15
+
16
+
Python versions supported:
17
+
18
+
* Python 3.8
19
+
* Python 3.7
20
+
* Python 3.6
21
+
* Python 3.5
22
+
23
+
24
+
**Note:** Python 2.7 support has been dropped.
25
+
26
+
.. note::
27
+
The driver may still work with older versions of python.
28
+
29
+
The previous driver `Python Driver 1.7`_ supports older versions of python,
30
+
the Neo4j 4.0 will work in fallback mode (using Bolt Protocol Version 3) with that driver.
31
+
32
+
33
+
****************
34
+
Breaking Changes
35
+
****************
36
+
37
+
Version Scheme Changes
38
+
======================
39
+
40
+
The version number have jumped from :code:`1.7` to :code:`Python Driver 4.0` to align with the Neo4j Database version scheme.
41
+
42
+
43
+
Namespace Changes
44
+
=================
45
+
46
+
:code:`import neo4j.v1` have changed namespace to be :code:`import neo4j`
47
+
48
+
49
+
Secure Connection
50
+
=================
51
+
52
+
Neo4j 4.0 is by default configured to use a non secure connection.
53
+
54
+
The Driver Configuration argument :code:`encrypted` is by default set to :code:`False`.
55
+
56
+
To be able to connect to Neo4j 3.5 set :code:`encrypted=True` to have it configured as the default for that setup.
57
+
58
+
59
+
Bookmark Changes
60
+
================
61
+
62
+
Bookmarks is now a Bookmark class instead of a string.
63
+
64
+
65
+
Exceptions Changes
66
+
==================
67
+
68
+
The exceptions in :code:`neo4j.exceptions` have been updated and there is internal exceptions starting with the naming :code:`Bolt` that should be propagated into the exceptions API.
69
+
70
+
71
+
URI Changes
72
+
===========
73
+
74
+
`bolt+routing` have been renamed to `neo4j`
75
+
76
+
77
+
Class Renaming Changes
78
+
======================
79
+
80
+
* :code:`BoltStatementResult` is now :code:`Result`
81
+
* :code:`StatementResultSummary` is now :code:`ResultSummary`
82
+
* :code:`Statement` is now :code:`Query`
83
+
84
+
85
+
Argument Renaming Changes
86
+
=========================
87
+
88
+
* :code:`statement` is now :code:`query`
89
+
* :code:`cypher` is now :code:`query`
90
+
* :code:`Session.run(cypher, ...` is now :code:`Session.run(query, ...`
91
+
* :code:`Transaction.run(statement, ...` is now :code:`Transaction.run(query, ...`
92
+
* :code:`StatementResultSummary.statement` is now :code:`ResultSummary.query`
93
+
* :code:`StatementResultSummary.statement_type` is now :code:`ResultSummary.query_type`
Copy file name to clipboardExpand all lines: docs/source/transactions.rst
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ For example::
25
25
26
26
To construct a :class:`.Session` use the :meth:`.Driver.session` method.
27
27
28
-
.. class:: neo4j.Session
28
+
.. class:: .Session
29
29
30
30
.. automethod:: close
31
31
@@ -75,7 +75,7 @@ Explicit transactions support multiple statements and must be created with an ex
75
75
This creates a new :class:`.Transaction` object that can be used to run Cypher.
76
76
It also gives applications the ability to directly control `commit` and `rollback` activity.
77
77
78
-
.. class:: neo4j.Transaction
78
+
.. class:: .Transaction
79
79
80
80
.. automethod:: run
81
81
@@ -127,7 +127,7 @@ Returning a live result object would prevent the driver from correctly managing
127
127
128
128
To exert more control over how a transaction function is carried out, the :func:`.unit_of_work` decorator can be used.
129
129
130
-
.. autofunction:: neo4j.unit_of_work
130
+
.. autofunction:: neo4j.work.simple.unit_of_work
131
131
132
132
133
133
Access modes
@@ -140,7 +140,7 @@ Note that this mode is simply a default and not a constraint.
140
140
This means that transaction functions within a session can override the access mode passed to that session on construction.
141
141
142
142
.. note::
143
-
The driver does not parse Cypher statements and cannot determine whether a statement tagged as `read` or `write` is tagged correctly.
144
-
Since the access mode is not passed to the server, this can allow a `write` statement to be executed in a `read` call on a single instance.
143
+
The driver does not parse Cypher queries and cannot determine whether the access mode should be :code:`ACCESS_READ` or :code:`ACCESS_WRITE`.
144
+
Since the access mode is not passed to the server, this can allow a :code:`ACCESS_WRITE` statement to be executed for a :code:`ACCESS_READ` call on a single instance.
145
145
Clustered environments are not susceptible to this loophole as cluster roles prevent it.
146
146
This behaviour should not be relied upon as the loophole may be closed in a future release.
0 commit comments