When you issue START VIOLATIONS TABLE for a target table, the violations table that the statement creates has a predefined structure. This structure consists of the columns of the target table and three additional columns.
The following table shows the schema of the violations table.
| Column Name | Data Type | Column Description | ||
|---|---|---|---|---|
| Same columns (in the same order) that appear in the target table | Same types as corresponding columns in the target table. | The violations table has the same schema as the target table, so that rows violating constraints or a unique-index during insert, update, and delete operations can be filtered to the violations table. | ||
| informix_tupleid | SERIAL | Unique serial code for the nonconforming row | ||
| informix_optype | CHAR(1) | The type of operation that caused this bad row. This column can have the following values: | ||
| I = | Insert | |||
| D = | Delete | |||
| O = | Update (with original values in this row) | |||
| N = | Update (with new values in this row) | |||
| S = | SET Database Object Mode (IDS only) | |||
| informix_recowner | CHAR(32) | User who issued the statement that created this nonconforming row | ||
Serial columns in the target table are converted to integer data types in the violations table.
Users can examine these nonconforming rows in the violations table, analyze the related rows that contain diagnostic information in the diagnostics table, and take corrective actions.
Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]