Skip to content

Conversation

lutovich
Copy link
Contributor

Previously, it was not possible to rollback transaction after failure. Doing this resulted in an error. This PR turns it into a no-op. Transaction is automatically rolled back after failure in the database because failure is acknowledged by sending a RESET message. So this is just a driver API level change.

Previously, it was not possible to rollback transaction after failure.
Doing this resulted in an error. This commit turns it into a no-op.
Transaction is automatically rolled back after failure in the database
because failure is acknowledged by sending a RESET message. So this is
just a driver API level change.
@lutovich lutovich requested a review from ali-ince September 14, 2018 16:45
Copy link
Contributor

@ali-ince ali-ince left a comment

Choose a reason for hiding this comment

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

LGTM.

@ali-ince ali-ince merged commit 92a946d into neo4j:1.7 Sep 20, 2018
@lutovich lutovich deleted the 1.7-tx-rollback-after-failure branch September 20, 2018 16:04
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