Skip to content

[4.4] Improve Neo4jError representation #805

New issue

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

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

Already on GitHub? # to your account

Merged
merged 3 commits into from
Sep 19, 2022

Conversation

robsdedude
Copy link
Member

When the error is not received from the DBMS, but instead originates from somewhere in the driver, it might not have a code and a message. In that case, we fall back to the default Exception representation.

Related:

When the error is not received from the DBMS, but instead originates from
somewhere in the driver, it might not have a code and a message. In that case,
we fall back to the default Exception representation.

Related:
 * neo4j#796
Even though, all errors that come from the server go through
`Noej4jError.hydrate` which (currently) makes sure that `code` *and* `message`
are set, this might change in the future.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3️⃣

@robsdedude robsdedude merged commit 154054b into neo4j:4.4 Sep 19, 2022
@robsdedude robsdedude deleted the improve-neo4j-error-message-4.4 branch September 19, 2022 12:49
@robsdedude robsdedude changed the title [4.4] Improve Noe4jError representation [4.4] Improve Neo4jError representation Sep 19, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants