Closed rsprinkle closed 5 years ago
Hi,
The warning is not about whether the statement is used, but about if there is a matching Java method in the corresponding mapper interface (mainly to avoid simple mistakes like typos). I believe the current behavior is reasonable because...
@rsprinkle Could you confirm @harawata 's comment?
Assuming my comment was a satisfactory answer. :D
A select statement that does not have a matching method in the mapper interface generates a warning even when it is used as part of a nested select in a resultMap.
I do not think the warning should be present if the statement is used within a mapper.