Interface ConfigBuilderInterfaces.MultiTableDataColumnStep4
- All Superinterfaces:
ConfigBuilderInterfaces.MultiTableAddTable, ConfigBuilderInterfaces.MultiTableAddTableOrExit, ConfigBuilderInterfaces.MultiTableDataColumnStep1, ConfigBuilderInterfaces.MultiTableExit
- All Known Subinterfaces:
ConfigBuilderInterfaces.MultiTableDataColumnStep2, ConfigBuilderInterfaces.MultiTableDataColumnStep3
- Enclosing class:
ConfigBuilderInterfaces
public static interface ConfigBuilderInterfaces.MultiTableDataColumnStep4
extends ConfigBuilderInterfaces.MultiTableDataColumnStep1
Fluent API to build a
MultiTableConfig
Follow the method chain to finally obtain the result with ConfigBuilderInterfaces.MultiTableExit.get().
- Author:
- Karl Eilebrecht
-
Method Summary
Modifier and TypeMethodDescriptionfilteredBy(String columnName, AdlSqlType columnType, String value) Defines an extra column filter on a column.Methods inherited from interface ConfigBuilderInterfaces.MultiTableAddTable
withTable, withTableMethods inherited from interface ConfigBuilderInterfaces.MultiTableDataColumnStep1
dataColumnMethods inherited from interface ConfigBuilderInterfaces.MultiTableExit
get
-
Method Details
-
filteredBy
ConfigBuilderInterfaces.MultiTableDataColumnStep4 filteredBy(String columnName, AdlSqlType columnType, String value) Defines an extra column filter on a column. This is required if the target column stores information effectively qualified or narrowed by values of other column(s).Note: The actual value (either hard-coded or from a variable) must be an ADL-value.
Example:
- correct:
filteredBy("ACTIVE", SQL_BOOLEAN, "1") - incorrect:
filteredBy("ACTIVE", SQL_BOOLEAN,"TRUE")
- Parameters:
columnName- name of another column of the same table to be tested for a fixed valuecolumnType- type of the filter column for sql generationvalue- the filter, a fixed value or variable placeholder ${varName} to include into any query related to the data column to filter the results- Returns:
- builder
- See Also:
- correct:
-