public class CompositeSingleOperandTypeChecker extends CompositeOperandTypeChecker implements SqlSingleOperandTypeChecker
SqlSingleOperandTypeChecker rules to be
combined into one rule.CompositeOperandTypeChecker.CompositionSqlOperandTypeChecker.ConsistencyallowedRules, composition| Modifier and Type | Method and Description |
|---|---|
boolean |
checkSingleOperandType(SqlCallBinding callBinding,
SqlNode node,
int iFormalOperand,
boolean throwOnFailure)
Checks the type of a single operand against a particular ordinal position
within a formal operator signature.
|
com.google.common.collect.ImmutableList<? extends SqlSingleOperandTypeChecker> |
getRules() |
checkOperandTypes, getAllowedSignatures, getConsistency, getOperandCountRange, isOptional, typeInferenceclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitcheckOperandTypes, getAllowedSignatures, getConsistency, getOperandCountRange, isFixedParameters, isOptional, typeInferencepublic com.google.common.collect.ImmutableList<? extends SqlSingleOperandTypeChecker> getRules()
getRules in class CompositeOperandTypeCheckerpublic boolean checkSingleOperandType(SqlCallBinding callBinding, SqlNode node, int iFormalOperand, boolean throwOnFailure)
SqlSingleOperandTypeCheckerFor example, when validating the actual call
C(X, Y, Z)
the strategy for validating the operand Z might involve checking its
type against the formal signature OP(W). In this case,
iFormalOperand would be zero, even though the position of Z
within call C is two.
Caution that we could not(shouldn't) implement implicit type coercion for this checker,
implicit type coercion has side effect(modify the AST), if this single operand checker is
subsumed in a composite rule(OR or AND), we can not make any side effect if we
can not make sure that all the single operands type check are passed(with type coercion).
But there is an exception: only if the call has just one operand, for this case,
use SqlOperandTypeChecker.checkOperandTypes(org.apache.calcite.sql.SqlCallBinding, boolean) instead.
checkSingleOperandType in interface SqlSingleOperandTypeCheckercallBinding - description of the call being checked; this is only
provided for context when throwing an exception; the
implementation should NOT examine the
operands of the call as part of the checknode - the actual operand to be checkediFormalOperand - the 0-based formal operand ordinalthrowOnFailure - whether to throw an exception if check fails
(otherwise returns false in that case)Copyright © 2012-2022 Apache Software Foundation. All Rights Reserved.