Add @StatementId
to support overloaded mapper methods
#1519
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 PR introduces a new annotation
@StatementId
to let users assign arbitrary statement ID [1].When the value is omitted, MyBatis will calculate the ID from the method signature.
e.g.
There is no documentation yet.
I haven't decided if this should be merged or not and there could be changes in the spec.
Should fix #1482 . Related to #1312 .
Any feedback is appreciated! 馃檹
[1] I plan to apply more strict validation to the user-specified ID. e.g. valid characters are alphanumeric, underscore, brackets
[]
and pound sign#
.