Neoview JDBC Type 4 Driver Programmer's Reference (R2.2, R2.3, R2.4, R2.5)

For example, the following command generates the SQL statements to create the triggers for the
base table sales.paris.pictures, which contains a BLOB column, and executes those
statements. Note: This command must be typed on one line.
java -Dhpt4jdbc.blobTableName=sales.paris.lobTable4pictures
com.hp.t4jdbc.T4LobAdmin
-trigger
-exec sales.paris.pictures
Limitations of LOB Data (CLOB and BLOB Data Types)
Limitations of the CLOB and BLOB data types, collectively referred to as LOB data, are:
• LOB columns can only be in the target column list of these SQL statements:
— INSERT statement
— Select list of a SELECT statement
— Column name in the SET clause of an UPDATE statement
• LOB columns cannot be referenced in the SQL functions and expressions.
• LOB data is not deleted from the LOB table when the base row is deleted unless a trigger is
established. For information about triggers, see “Using SQL Triggers to Delete LOB Data”
(page 62).
• LOB data is not accessible if the base table name is changed.
• LOB columns cannot be copied to another table by using Neoview utility commands; for
example, through HP Neoview DB Admin.
• The name of a base table that has CLOB or BLOB columns must be unique across all catalogs
and schemas when more than one of these base tables share a single LOB table.
NOTE: Adding a trigger can affect up to three schemas. For each schema, you must either own
the schema or be the super ID.
• The schema where the trigger is created.
• The schema where the subject table (LOB table) exists.
• The schema where the referenced table (base table) exists.
Limitations of LOB Data (CLOB and BLOB Data Types) 63