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.

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

Ambiguous collection type bug fix. Ref #364 #1472

Merged
merged 1 commit into from Jan 30, 2019

Conversation

helloyou2012
Copy link
Contributor

@helloyou2012 helloyou2012 commented Jan 30, 2019

<collection /> does not have resultType attribute. Is it javaType?

@harawata
Copy link
Member

Thank you, @helloyou2012 !

Did you get this error with your solution?
We might need to release 3.5.1 for this...

@harawata harawata self-assigned this Jan 30, 2019
@harawata harawata added the bug label Jan 30, 2019
@harawata harawata added this to the 3.5.1 milestone Jan 30, 2019
@harawata harawata merged commit 19d259f into mybatis:master Jan 30, 2019
harawata added a commit that referenced this pull request Jan 30, 2019
@harawata
Copy link
Member

Hi @helloyou2012 ,

This should be fixed in the latest 3.5.1-SNAPSHOT.
Are you OK with using SNAPSHOT for a while?
If not, I'll consult with the team.

I'm sorry for the inconvenience and thank you again for the PR!

Regards,
Iwao

@helloyou2012
Copy link
Contributor Author

Thanks @harawata, I use 3.4.6 for a while.

@harawata
Copy link
Member

@helloyou2012 ,

I'm sorry about the regression and appreciate your patience.
As there were many changes made in 3.5.0, I think we should wait for a while to see if there is any other issues.

pulllock pushed a commit to pulllock/mybatis-3 that referenced this pull request Oct 19, 2023
Corrected incorrect attribute name to avoid false positive error.
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants