-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CALCITE-6819] MSSQL doesn't support TRUE/FALSE keywords in its Join predicate #4192
base: main
Are you sure you want to change the base?
Conversation
…predicate In MSSQL dialect use 1=1 instead of TRUE
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
core/src/main/java/org/apache/calcite/sql/dialect/MssqlSqlDialect.java
Outdated
Show resolved
Hide resolved
core/src/test/java/org/apache/calcite/rel/rel2sql/RelToSqlConverterTest.java
Show resolved
Hide resolved
…predicate PR comments
@@ -196,4 +197,12 @@ public static SqlSpecialOperator specialOperatorByName(String opName) { | |||
} | |||
}; | |||
} | |||
|
|||
public static void writeAlwaysCondition(SqlWriter writer, boolean value) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method requires some annotations to clarify that some databases require converting True to '1=1' and false to '1=0'.
writer.sep(SqlStdOperatorTable.EQUALS.getName()); | ||
writer.literal(value ? "1" : "0"); | ||
writer.endList(frame); | ||
writeAlwaysCondition(writer, value); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unparseBoolLiteralToCondition?
In MSSQL dialect use 1=1 instead of TRUE