Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sreeharshar84
Copy link
Contributor

In MSSQL dialect use 1=1 instead of TRUE

…predicate

In MSSQL dialect use 1=1 instead of TRUE
Copy link
Contributor

@suibianwanwank suibianwanwank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@@ -196,4 +197,12 @@ public static SqlSpecialOperator specialOperatorByName(String opName) {
}
};
}

public static void writeAlwaysCondition(SqlWriter writer, boolean value) {
Copy link
Contributor

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);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unparseBoolLiteralToCondition?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants