修复OceanBase validateQuery问题 #4966
Closed
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
|
|
|
已验证测试通过 |
|
等待OB驱动包开源到maven仓库中，目前我是手动安装到本地仓库的 |
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.
当前druid针对oceanbase区分租户的方式是通过jdbc中前缀，但是其实oceanbase无论是mysql租户还是oracle租户jdbc连接方式都可以是jdbc:oceanbase://host:port，所以这种区分方式是不准确的（会报错），目前oceanbase内部区分主要是通过与ob server通信，获取当前是什么租户，然后在oceanbaseBaseConnection中protocol中isOracleMode判断是否是oracle租户