Skip to content

Section default_access_mode in Session had ACCESS_READ/WRITE instead of READ/WRITE_ACCESS. #839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 25, 2022
Merged

Section default_access_mode in Session had ACCESS_READ/WRITE instead of READ/WRITE_ACCESS. #839

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/source/api.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -686,11 +686,11 @@ access mode passed to that session on construction.

.. note::
The driver does not parse Cypher queries and cannot determine whether the
access mode should be ``neo4j.ACCESS_WRITE`` or ``neo4j.ACCESS_READ``.
access mode should be ``neo4j.WRITE_ACCESS`` or ``neo4j.READ_ACCESS``.
This setting is only meant to enable the driver to perform correct routing,
*not* for enforcing access control. This means that, depending on the server
version and settings, the server or cluster might allow a write-statement to
be executed even when ``neo4j.ACCESS_READ`` is chosen. This behaviour should
be executed even when ``neo4j.READ_ACCESS`` is chosen. This behaviour should
not be relied upon as it can change with the server.

:Type: ``neo4j.WRITE_ACCESS``, ``neo4j.READ_ACCESS``
Expand Down