docs: Fix SqlSession direct API usage caveats based on actual behavior(#531) #1170
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mybatis#531) This commit updates the documentation for the direct use of the raw MyBatis SqlSession API, resolving the long-standing discrepancy reported in mybatis#531. The previous documentation incorrectly stated that using SqlSession.openSession() within a Spring transaction would "throw an exception" and "not participate in any Spring transactions." The revised documentation reflects the actual behavior.
Contributor
Author
|
Hi maintainers, It seems like the CI workflow is failing due to a setup issue with the JDK 26-ea environment ( Since this PR only involves a documentation update (no Java code changes), the failure is likely unrelated to my commit. Could you please trigger a re-run of the failed jobs? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates the documentation for the direct use of the raw MyBatis SqlSession API, resolving the long-standing discrepancy reported in #531.
The previous documentation incorrectly stated that using SqlSession.openSession() within a Spring transaction would "throw an exception" and "not participate in any Spring transactions."
The revised documentation reflects the actual behavior.