Introduce reasonable transaction boundaries for multi query operations #2860
Assignees
Milestone
Comments
meistermeier
added a commit
that referenced
this issue
Feb 12, 2024
If no transactional boundaries were set by the user, Spring Data Neo4j would create new transactions (default read/write) for the underlying database operations. In cases where multiple statements are required to execute a SDN operation this would mean that multiple transaction would have been created. This commit fixes this problem and creates new transaction if no transaction was defined around the invocation of those units-of-work. The change will introduce a breaking change: All pure read operations in SDN (like Neo4jTemplate#findAll) will now happen in read-only transactions. If they contain custom statements with write operations, they need to get wrapped in an explicit write transaction. Closes #2860 Co-authored-by: Michael Simons <michael@simons.ac>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Be it save with relationships or loading of cyclic graph data, both operations will issue multiple queries.
If the user does not specify transactions via
@TransactionalorTransactionTemplate/TransactionalOperator, each query will happen in its own transaction. To avoid this surprising scenario for the users we should create transactions around those batches of operations if the user does not specify a broader transactional scope.The text was updated successfully, but these errors were encountered: