Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Helpful error message when using multiple `@AutomapConstructor` with `argNameBasedConstructorAutoMapping` setting
See original GitHub issueI figured I could use multiple @AutomapConstructor annotations in a class when using argNameBasedConstructorAutoMapping setting.
It seems to work pretty well in the dev environment (just lucky) but in real environment Mybatis throws an exception with a message of the form below.
Constructor auto-mapping of ''{1}'' failed because ''{0}'' were not found in the result set Available columns are ''{2}'' and mapUnderscoreToCamelCase is ''{3}''."
This kind of message does not provide enough clues to find the root cause.
I think it’s good to be precise with the error message.
Please check the PR https://github.com/mybatis/mybatis-3/pull/2627. Thank you.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s a ‘known issue’ ™️ We decided not to fix it because there may be many existing solutions that rely on the current behavior without realizing it.
Thank you for the explanation and the PR, @sogoagain !