Skip to content

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 force-pushed the jdbc3keygenerator-npe branch from 51e0de7 to 3496397 Compare November 11, 2019 17:58
@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