Extended attributes views

The extended attributes view tool generates database views that reference the data for extended attributes.

For each model object that has extended attributes, the tool creates an SQL script that when run, creates two extended attribute views:
  • EA_model_V that has columns corresponding to the extended attributes. Each extended attribute can be joined to the corresponding building block view, BB_model_V, using the PK_C column.
  • Fix Pack 1 BE_model_V that has columns corresponding to the Common Data Model attributes and to the extended attributes. When the column name conflict occurs, the extended attribute columns might not be present.

All extended attributes on the same model object type are in the same database view.

The scripts depend on the current definitions of extended attributes. The tool does not check the attributes that were created and removed, even though such attributes with values are still assigned to some objects. If you modify an extended attribute, you must drop the existing view before you use the extended attribute view tool to create an updated SQL script and an updated attribute view.

Fix Pack 3

Data type modification

In TADDM 7.3.0.2, and earlier, the extattr_views.sh script creates extended attributes views with columns of type CLOB. Starting with 7.3.0.3, the views contain data of specific types, for example, VARCHAR, or SMALLINT. The following table provides the new column types in the extended attributes views in DB2 and Oracle databases.
Table 1. Extended attributes views column types in DB2 and Oracle databases
GUI type Column type in DB2 Column type in Oracle
String VARCHAR(32000) VARCHAR2(4000)
Character VARCHAR(4) VARCHAR2(4)
Double precision floating point DOUBLE NUMBER
Floating point REAL NUMBER
Boolean SMALLINT NUMBER(1)
Integer INTEGER NUMBER
Short integer SMALLINT NUMBER
Long integer BIGINT NUMBER
Such modification might affect integration with products that use TADDM database views for extended attributes. For example, if you use BIRT reports, errors might be generated if extended attributes columns are not cast to a specific data type, for example, VARCHAR.
Note: In TADDM 7.3.0.2, and earlier, extended attributes of the boolean type are displayed as false, or true in the database views. In TADDM 7.3.0.3, and later, the value is an integer, either 0, or 1. It means that the BIRT and Cognos reports that were created before this change are not compatible with the new data types.