Mapping of Native to TDV Data Types Across TDV Versions
As of version 7.0, TDV supports the BOOLEAN data type. One result is that BOOL or BOOLEAN data types in data sources are now mapped to BOOLEAN in TDV rather than to CHAR or BIT.
Effects of this change can include:
• Existing caches (target tables) may become incompatible and may have to be re-created.
• Parts of queries that used to push completely may not push now.
• Some views and procedures may be impacted if, for example, they apply some function to the column introspected as a CHAR, and now that it is a BOOLEAN it is no longer a valid argument for that function (or operator, clause, and so on).
• If a column was used in a JOIN criterion or a WHERE predicate, the column might now require an explicit CAST to be compared to another value.
Possible remedies include:
• Re-create incompatible caches or target tables created in TDV versions prior to 7.0.
• Remap BOOLEAN back to CHAR or BIT in values.xml and reintrospect the data source.