Package de.calamanari.adl.sql.config

Interface ConfigBuilderInterfaces.MultiTableStep2

All Superinterfaces:

ConfigBuilderInterfaces.MultiTableStep3

All Known Subinterfaces:

ConfigBuilderInterfaces.MultiTableStep1

Enclosing class:

ConfigBuilderInterfaces

public static interface ConfigBuilderInterfaces.MultiTableStep2
extends ConfigBuilderInterfaces.MultiTableStep3

Fluent API to build a MultiTableConfig

Follow the method chain to finally obtain the result with ConfigBuilderInterfaces.MultiTableExit.get().

Method Summary

Modifier and Type	Method	Description
ConfigBuilderInterfaces.MultiTableStep3	withSparseData()	Tells the query builder that the data in this table may be sparse, so data from a single row may not tell the full picture.
ConfigBuilderInterfaces.MultiTableStep3	withUniqueIds()	Tells the query builder that for the same record (ID) there is either exactly one row or no row.

Methods inherited from interface de.calamanari.adl.sql.config.ConfigBuilderInterfaces.MultiTableStep3

filteredBy, idColumn

Method Details

withSparseData

ConfigBuilderInterfaces.MultiTableStep3 withSparseData()

Tells the query builder that the data in this table may be sparse, so data from a single row may not tell the full picture.

Returns:

builder

See Also:

• SingleTableConfig

withUniqueIds

ConfigBuilderInterfaces.MultiTableStep3 withUniqueIds()

Tells the query builder that for the same record (ID) there is either exactly one row or no row. In other words, selecting the ID column from this won't return any duplicates (a logical unique constraint).

This setting is vital for negative queries. Let TBL be a table with the columns ID and COLOR and the record for ID=4711 has two rows in it, one for color=red and another for color=blue. If you now make a query COLOR<>'blue' you get a wrong answer. Based on this setting the converter can decide to add an existence check to avoid this problem.

Returns:

builder

See Also:

• SingleTableConfig