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
Copy file name to clipboardExpand all lines: docs/source/api.rst
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The :class:`neo4j.Driver` construction is done via a `classmethod` on the :class
17
17
:members: driver
18
18
19
19
20
-
Example, driver creation:
20
+
Driver creation example:
21
21
22
22
.. code-block:: python
23
23
@@ -39,7 +39,7 @@ This will implicitly create a :class:`neo4j.Auth` with a ``scheme="basic"``.
39
39
Other authentication methods are described under :ref:`auth-ref`.
40
40
41
41
42
-
Example, with block context:
42
+
``with`` block context example:
43
43
44
44
.. code-block:: python
45
45
@@ -331,7 +331,8 @@ For example:
331
331
332
332
Connection details held by the :class:`neo4j.Driver` are immutable.
333
333
Therefore if, for example, a password is changed, a replacement :class:`neo4j.Driver` object must be created.
334
-
More than one :class:`.Driver` may be required if connections to multiple databases, or connections as multiple users, are required.
334
+
More than one :class:`.Driver` may be required if connections to multiple databases, or connections as multiple users, are required,
335
+
unless when using impersonation (:ref:`impersonated-user-ref`).
335
336
336
337
:class:`neo4j.Driver` objects are thread-safe but cannot be shared across processes.
337
338
Therefore, ``multithreading`` should generally be preferred over ``multiprocessing`` for parallel database access.
@@ -371,7 +372,7 @@ All database activity is co-ordinated through two mechanisms: the :class:`neo4j.
371
372
372
373
A :class:`neo4j.Session` is a logical container for any number of causally-related transactional units of work.
373
374
Sessions automatically provide guarantees of causal consistency within a clustered environment but multiple sessions can also be causally chained if required.
374
-
Sessions provide the top-level of containment for database activity.
375
+
Sessions provide the toplevel of containment for database activity.
375
376
Session creation is a lightweight operation and *sessions are not thread safe*.
376
377
377
378
Connections are drawn from the :class:`neo4j.Driver` connection pool as required.
Copy file name to clipboardExpand all lines: docs/source/async_api.rst
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The :class:`neo4j.AsyncDriver` construction is done via a `classmethod` on the :
23
23
:members: driver
24
24
25
25
26
-
Example, driver creation:
26
+
Driver creation example:
27
27
28
28
.. code-block:: python
29
29
@@ -49,7 +49,7 @@ For basic authentication, ``auth`` can be a simple tuple, for example:
49
49
This will implicitly create a :class:`neo4j.Auth` with a ``scheme="basic"``.
50
50
Other authentication methods are described under :ref:`auth-ref`.
51
51
52
-
Example, with block context:
52
+
``with`` block context example:
53
53
54
54
.. code-block:: python
55
55
@@ -197,7 +197,8 @@ For example:
197
197
198
198
Connection details held by the :class:`neo4j.AsyncDriver` are immutable.
199
199
Therefore if, for example, a password is changed, a replacement :class:`neo4j.AsyncDriver` object must be created.
200
-
More than one :class:`.AsyncDriver` may be required if connections to multiple databases, or connections as multiple users, are required.
200
+
More than one :class:`.AsyncDriver` may be required if connections to multiple databases, or connections as multiple users, are required,
201
+
unless when using impersonation (:ref:`impersonated-user-ref`).
201
202
202
203
:class:`neo4j.AsyncDriver` objects are safe to be used in concurrent coroutines.
203
204
They are not thread-safe.
@@ -236,7 +237,7 @@ All database activity is co-ordinated through two mechanisms: the :class:`neo4j.
236
237
237
238
A :class:`neo4j.AsyncSession` is a logical container for any number of causally-related transactional units of work.
238
239
Sessions automatically provide guarantees of causal consistency within a clustered environment but multiple sessions can also be causally chained if required.
239
-
Sessions provide the top-level of containment for database activity.
240
+
Sessions provide the toplevel of containment for database activity.
240
241
Session creation is a lightweight operation and *sessions cannot be shared between coroutines*.
241
242
242
243
Connections are drawn from the :class:`neo4j.AsyncDriver` connection pool as required.
0 commit comments