Join.java 中 SQLConfig outerConfig 重命名成 onConfig,然后用原来的 outerConfig 增加最外层的where 查询条件 - #829
Merged
TommyLemon merged 3 commits intoJul 20, 2025
Merged
TommyLemon merged 3 commits into
TommyLemon merged 3 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
… 方法，然后再加回来 SQLConfig outerConfig，然后下方的键值对放到 outerConfig 上，后面再具体 AbstractSQLConfig gainWhereString。 1、inner join 本身是最外面增加条件，没有增加 2、onConfig "@group": "key2+" // JOIN 外层 GROYP BY key2 "@having": "count(key3)>0" // JOIN 外层 HAVING count(key3)>0 "@order": "key2+,key3-" // JOIN 外层 ORDER BY key2 ASC, key3 DESC 本身这些条件就是加到最外层。
TommyLemon
approved these changes
Jul 20, 2025
Copy link
Copy Markdown
Contributor
Author
|
这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。
|
Sorry, something went wrong.
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.
AbstractSQLConfig gainWhereString 增加适配逻辑.
1.inner join 本身是最外面增加条件，忽略这种情况
2.onConfig "@group": "key2+" // JOIN 外层 GROYP BY key2
"@having": "count(key3)>0" // JOIN 外层 HAVING count(key3)>0
"@order": "key2+,key3-" // JOIN 外层 ORDER BY key2 ASC, key3 DESC 本身这些条件就是加到最外层。
"join": { "</Location_info/code@": { "id": "88888", "@column": "key2,key3", "@group": "key2+", "@having": "count(key3)>0", "@order": "key2+,key3-" }, "id": "88888",只有这个条件加 on 上. 其他 "@group": "key2+","@having": "count(key3)>0", "@order": "key2+,key3-" 都是加到 最外面的where条件上.