Interface ConfigBuilderInterfaces.SingleTableDataColumnStep3
- All Superinterfaces:
ConfigBuilderInterfaces.SingleTableAddColumnOrExit, ConfigBuilderInterfaces.SingleTableDataColumnStep4
- All Known Subinterfaces:
ConfigBuilderInterfaces.SingleTableDataColumnStep2
- Enclosing class:
ConfigBuilderInterfaces
SingleTableConfig
Follow the method chain to finally obtain the result with ConfigBuilderInterfaces.SingleTableAddColumnOrExit.get().
- Author:
- Karl Eilebrecht
-
Method Summary
Modifier and TypeMethodDescriptionmultiRow()Defines that the data for a single record can be spread across multiple rows.Methods inherited from interface ConfigBuilderInterfaces.SingleTableAddColumnOrExit
dataColumn, getMethods inherited from interface ConfigBuilderInterfaces.SingleTableDataColumnStep4
filteredBy
-
Method Details
-
multiRow
Defines that the data for a single record can be spread across multiple rows.This property must be set if the same column is mapped to multiple attributes (with filter column(s), see example below) or if this is a collection attribute and you want to allow AND for two conditions of the same attribute (e.g.,
color=blue AND color=red.Example:
+------+------------+-------------+ | ID | ENTRY_TYPE | ENTRY_VALUE | +------+------------+-------------+ | 8599 | MODEL | X4886 | +------+------------+-------------+ | 8599 | BRAND | QUACK | +------+------------+-------------+ | 8599 | COLOR | BLACK | +------+------------+-------------+ | ... | ... | ... |
Let's say we want to querymodel=X4886 AND brand=QUACK.Obviously, from the table above you cannot query
... WHERE ENTRY_TYPE='MODEL' AND ENTRY_VALUE='X4886' AND ENTRY_TYPE='BRAND' AND ENTRY_VALUE='QUACK'The problem is that the first condition would fix the row, so the second condition will never become true (accidental row-pinning).
With the multi-row you tell the query builder about this problem and enforce a different query style.
- Returns:
- builder
- See Also:
-