Repository navigation
Conversation
整理开发分支 3cc0a1c 相对上游 main 的变更,保留模式识别、SQL 与 JDBC 适配及回归基线。 Refs APIJSON#868, APIJSON#855
(cherry picked from commit ef417ed84b1bbf4939c46e6898dc8572a784a386)
(cherry picked from commit cb69449d05c86a526bb845aadc8115416973bde4)
(cherry picked from commit 7a369df8fa940e4d17b281fc2bc3f31390f10bcd)
(cherry picked from commit d77cfa11f9462639c3b06bc9c278742ec160e4bf)
保留 DISTINCT 分页断言;单行聚合遵循上游 APIJSON#885,不再要求 OFFSET/FETCH。
Contributor
Author
|
@TommyLemon 您好,本 PR 的 Maven 构建与测试已通过。目前 CI 失败发生在后续的 Update dependency graph 步骤,上传依赖快照时返回 403:Resource not accessible by integration。 看起来是 fork PR 的只读令牌无法向上游提交依赖快照,请帮忙确认此类 PR 是否应跳过该上传步骤。感谢审阅。 |
TommyLemon
approved these changes
Nov 21, 2026
This branch has not been deployed
This file contains hidden or 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
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.
变更说明
本 PR 是 #868 的后续修复,针对真实数据库验证中发现的问题,完善 KingbaseES MySQL、Oracle、SQL Server 三种兼容模式下的 SQL 生成、JDBC 执行及数据类型处理,并补充回归测试。
主要改动
KINGBASE_AUTO配置入口,通过SHOW database_mode识别实际兼容模式,按数据源缓存识别结果并选择对应方言。HAVING别名解析、生成主键回读及存储过程调用。配置兼容性
本次统一使用
KINGBASE_AUTO作为三种兼容模式的配置入口:@database或后端DEFAULT_DATABASE配置为KINGBASE_MYSQL、KINGBASE_ORACLE、KINGBASE_SQLSERVER的项目,需要改为KINGBASE_AUTO。KINGBASE入口保持原行为,不自动探测兼容模式。该调整涉及已有接入配置,迁移方式已补充到中文文档中,请维护者重点确认是否需要保留旧配置入口作为过渡。
Kingbase JDBC 驱动仍由应用提供。核心 ORM 不新增生产驱动依赖,Maven 中仅增加可选的驱动测试配置。
测试验证
Maven 构建及已执行的自动化回归测试通过,原生数据库行为基线比对未发现差异。
实库验证使用以下数据库及 JDBC 驱动版本:
V009R003C018PS0089.0.0-v9r3c18b0003V009R002C016PS0039.0.0-v9r2c16b0006V009R004C0199.0.0-v9r4c19b0004已针对三种兼容模式中本次改动涉及的功能进行定向实库验证,主要覆盖以下场景:
HAVING别名解析、存储过程调用、模式识别、生成主键回读及参数化 CRUD。上述已执行的定向实库验证均通过。
后续将继续补充边界场景测试;如发现兼容性问题,会补充相应修复和回归用例。