Skip to content

Conversation

@kazuki43zoo
Copy link
Member

Fixes #1334

I've added the DEFAULT as new enum element. It become the same behavior with unset at xml mapper.

@harawata
Copy link
Member

harawata commented Sep 5, 2018

Thank you, @kazuki43zoo !

It looks good as it is, but how about adding null check to the builder?

mappedStatement.resultSetType = resultSetType == null ? ResultSetType.DEFAULT : resultSetType;

Then we may be able to omit null check from the statement handlers.

kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this pull request Sep 6, 2018
@kazuki43zoo
Copy link
Member Author

@harawata Thanks for your advice!
I've fixed it,

@kazuki43zoo kazuki43zoo force-pushed the gh-1334_resultSetType branch from ffaa58b to 788236f Compare September 6, 2018 06:05
@kazuki43zoo kazuki43zoo merged commit 8efb2cc into mybatis:master Sep 7, 2018
@kazuki43zoo kazuki43zoo deleted the gh-1334_resultSetType branch September 7, 2018 16:51
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this pull request Sep 13, 2018
harawata added a commit to mybatis/mybatis.github.io that referenced this pull request Dec 5, 2018
pulllock pushed a commit to pulllock/mybatis-3 that referenced this pull request Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this pull request Oct 19, 2023
Change the default resultSetType to DEFAULT(same as unset) at annotation option
pulllock pushed a commit to pulllock/mybatis-3 that referenced this pull request Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants