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

Avoid invoking equals/hashCode when assigning generated keys #1728

Merged
merged 1 commit into from Nov 12, 2019

Conversation

harawata
Copy link
Member

When detecting single parameter case, it now checks parameter name instead of equality of the parameter objects.
This should fix gh-1719.

A caveat : when there is only one parameter and its name is 'param2' (for whatever reason), keyProperty must include the parameter name i.e. keyProperty="param2.xx".

When detecting single parameter case, it now checks parameter name instead of equality of the parameter objects.
This should fix mybatisgh-1719.

A caveat : when there is only one parameter and its name is 'param2' (for whatever reason), `keyProperty` must include the parameter name i.e. `keyProperty="param2.xx"`.
@harawata harawata merged commit a262898 into mybatis:master Nov 12, 2019
pulllock pushed a commit to pulllock/mybatis-3 that referenced this pull request Oct 19, 2023
Avoid invoking equals/hashCode when assigning generated keys
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.

Possible NullPointerException when assigning generated keys to objects with custom hashCode() method
1 participant