Skip to content

Avoid Results try to pull more records after transaction fail #1145

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 2 commits into from
Oct 10, 2023

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Oct 4, 2023

When two or more queries are running concurrent in the same transaction, a failure happenning in any of the queries implies in a broken transaction and any new message to the server should result in a error since the server state will be in failure.

Notifying all open results in the transaction about any error avoids any new message to be send by these objects.

@bigmontz bigmontz force-pushed the 5.x-transaction-termination-handling branch from 5a9803f to 458ba32 Compare October 6, 2023 08:44
When two or more queries are running concurrent in the same transaction, a failure happenning in any of the queries implies in a broken transaction and any new message to the server should result in a error since the server state will be in failure.

Notifying all open results in the transaction about any error avoids any new message to be send by these objects.
@bigmontz bigmontz force-pushed the 5.x-transaction-termination-handling branch from 458ba32 to efdc58d Compare October 10, 2023 12:07
@bigmontz bigmontz merged commit e26619c into neo4j:5.0 Oct 10, 2023
@bigmontz bigmontz deleted the 5.x-transaction-termination-handling branch October 10, 2023 14:22
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