Package de.calamanari.adl.sql.config

Interface ConfigBuilderInterfaces.SingleTableStep3

All Superinterfaces:

ConfigBuilderInterfaces.SingleTableStep4

All Known Subinterfaces:

ConfigBuilderInterfaces.SingleTableStep2

Enclosing class:

ConfigBuilderInterfaces

public static interface ConfigBuilderInterfaces.SingleTableStep3
extends ConfigBuilderInterfaces.SingleTableStep4

Fluent API to build a SingleTableConfig

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

Method Summary

Modifier and Type	Method	Description
ConfigBuilderInterfaces.SingleTableStep4	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.SingleTableStep4	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.SingleTableStep4

filteredBy, idColumn

Method Details

withSparseData

ConfigBuilderInterfaces.SingleTableStep4 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.SingleTableStep4 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