Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use method signature to resolve resultType of <select> #2767

Merged
merged 2 commits into from
Jan 6, 2023
Merged

Use method signature to resolve resultType of <select> #2767

merged 2 commits into from
Jan 6, 2023

Conversation

FlyInWind1
Copy link
Contributor

In our work time it's is possible to write a error resultType in mapper.xml. I think we can resolve resultType by namespce and id in mapper.xml, then we can avoid this error

@coveralls
Copy link

Coverage Status

Coverage: 87.326% (+0.01%) from 87.313% when pulling d51f3a7 on FlyInWind1:no-result-type into 35262b0 on mybatis:master.

@harawata harawata changed the title Resolve resultType by namespace and id when not provide resultType and resultMap Use method signature to resolve resultType of <select> Jan 6, 2023
@harawata harawata self-assigned this Jan 6, 2023
@harawata harawata added the enhancement Improve a feature or add a new feature label Jan 6, 2023
@harawata harawata added this to the 3.5.12 milestone Jan 6, 2023
@harawata harawata merged commit 2d50c4b into mybatis:master Jan 6, 2023
@harawata
Copy link
Member

harawata commented Jan 6, 2023

Thank you, @FlyInWind1 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@harawata harawata

Labels
enhancement Improve a feature or add a new feature
Projects
None yet
Milestone
3.5.12
Development

Successfully merging this pull request may close these issues.
3 participants
@FlyInWind1 @coveralls @harawata