What are the limitations with LANSA DB Triggers?

• LANSA DB triggers only work correctly for tables that are accessed via Native I/O.
  This excludes:

• RDMLX Other Tables that are only accessed via SQL, as well as

• LANSA tables containing one or more LOB fields or fields that are promoted to being stored as LOBs in the database.

• The IBM i DB2 UDB for IBM i Database Programming manual warns "An SQL update operation involves a simultaneous read operation followed by a write operation. Read triggers will not be run for SQL update operations. An update trigger should be specified to cover this read followed by a write operation."  The implementation of LANSA DB Triggers will simply cause the update processing to occur in this situation.

• No virtual column processing or validation will occur as part of LANSA DB Triggers. In particular, LANSA trigger functions will not have available to them the values of any virtual columns or PJC.

• Validation rules and LANSA trigger functions that are defined on a "where used" basis for real fields will always be executed when called via LANSA DB Triggers.