Skip to content

TransactionError on session.run() on busy session #1170

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.

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
May 15, 2025

Conversation

robsdedude
Copy link
Member

Raise TransactionError (subclass of DriverError) instead of ClientError (subclass of Neo4jError) when calling session.run() while an explicit transaction is active on that session.

  • This improves the differentiation between DriverError for client-side errors and Neo4jError for server-side errors.
  • It is now the same error raised as when trying to start an explicit transaction while another explicit transaction is already active.

Copy link
Contributor

@AndyHeap-NeoTech AndyHeap-NeoTech left a comment

Choose a reason for hiding this comment

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

LGTM

@robsdedude robsdedude merged commit ea8d1fa into neo4j:6.x May 15, 2025
20 checks passed
@robsdedude robsdedude deleted the errors/tx-error-on-busy-session branch May 15, 2025 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants