fix 数据源创建失败缺少cause(#653) #657
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. 修复(baomidou#653) 2. 为所有的数据源创建时进行初始化的都添加统一的异常包装返回. 为什么不对延迟加载的也做处理? 我能想到的处理办法时是对原始数据源进行一层wrapper, 都是在getConnection的时候进行初始化的，但是如何对数据源创建失败是一个比较难以判断的事情也没有多大的必要
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
为什么不对延迟加载的也做处理?
我能想到的处理办法时是对原始数据源进行一层wrapper, 都是在getConnection的时候进行初始化的，但是如何对数据源创建失败是一个比较难以判断的事情也没有多大的必要
What kind of change does this PR introduce? (check at least one)
The description of the PR:
Other information: