class |
AbstractDBBooleanConnectorFunctionSymbol
For AND, OR, etc.
|
class |
AbstractDBInequalityOperator |
class |
AbstractDBIsNullOrNotFunctionSymbol |
class |
AbstractDBIsStringEmptyFunctionSymbol |
class |
AbstractDBNonStrictEqOperator |
class |
AbstractDBStrictEqNeqFunctionSymbol |
class |
AbstractOrNullFunctionSymbol
Implementing the ternary logic for situations like:
* NULL AND y AND ...
|
class |
DBContainsFunctionSymbolImpl |
class |
DBLikeFunctionSymbolImpl |
class |
DefaultDBAndFunctionSymbol |
class |
DefaultDBBooleanInequalityOperator |
class |
DefaultDBDateInequalityOperator |
class |
DefaultDBDatetimeInequalityOperator |
class |
DefaultDBDefaultInequalityOperator |
class |
DefaultDBIsTrueFunctionSymbol |
class |
DefaultDBNonStrictDateEqOperator |
class |
DefaultDBNonStrictDatetimeEqOperator |
class |
DefaultDBNonStrictDefaultEqOperator
Cannot be simplified --> has to be evaluated by the DB engine
Only suitable for DB terms
|
class |
DefaultDBNonStrictNumericEqOperator |
class |
DefaultDBNonStrictStringEqOperator |
class |
DefaultDBNotFunctionSymbol |
class |
DefaultDBNumericInequalityOperator |
class |
DefaultDBOrFunctionSymbol |
class |
DefaultDBStrEndsWithFunctionSymbol |
class |
DefaultDBStrictEqFunctionSymbol
TODO: should it make it a non-DB boolean function symbol?
--> that is, downgrading to a non-strict equality?
|
class |
DefaultDBStrictNEqFunctionSymbol
TODO: should it make it a non-DB boolean function symbol?
--> that is, downgrading to a non-strict equality?
|
class |
DefaultDBStringInequalityOperator |
class |
DefaultDBStrStartsWithFunctionSymbol |
class |
FalseOrNullFunctionSymbolImpl |
class |
MockupDBIsNullOrNotFunctionSymbolImpl |
class |
OneDigitDBIsTrueFunctionSymbolImpl
The JDBC driver of DB2 may return the boolean as "0" or "1"
|
class |
OneLetterDBIsTrueFunctionSymbolImpl
The JDBC driver of Postgres may return the boolean as "t" or "f"
|
class |
SQLServerDBIsTrueFunctionSymbolImpl |
class |
StandardNotationDBBooleanFunctionSymbolImpl |
class |
TrueOrNullFunctionSymbolImpl |