-
Notifications
You must be signed in to change notification settings - Fork 358
breaking change for @Lock on String methods #2023
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
Conversation
Signed-off-by: mipo256 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
spring-data-jdbc/src/main/java/org/springframework/data/jdbc/repository/query/StringBasedJdbcQuery.java:149
- Replacing a warning with an exception for unsupported @lock usage is a breaking change. Ensure that clients invoking this API update to handle this exception and consider adding tests or documentation to clarify the new behavior.
throw new UnsupportedOperationException(LOCKING_IS_NOT_SUPPORTED + queryMethod);
Don't be scared, I requested out of interest a review from GitHub's copilot to see what happens. I never tried that so treat it as experiment. |
571fd96
to
1f2e694
Compare
Thanks. That's merged in 4.0.x |
This PR completes the discussion here, but is a breaking change anyway, so I decided to clean up some APIs that were for removal anywhay.