SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Messages Manual—523730-004
10-6
Recovery. Change the data you are attempting to enter to be consistent with the
constraint. The data must exist in another table. For example, if you are trying to enter
a department number for an employee, the department number must exist in a
department number table.
SQL 8104
Where view name1 is the name of the view.
Where name2 is the name of the table.
Cause. You attempted to perform an operation on table name1. The operation has
been prevented by the check on view name2, cascaded from the check option on the
table.
Effect. The operation fails.
Recovery. Change the view properties, if appropriate.
SQL 8105
Where name is the name of the view.
Cause. You attempted to perform an operation on table name that is prevented by the
check option on view name.
Effect. The operation fails.
Recovery. Insert into the base table rather than this view.
SQL 8106
Cause. The last row fetched by the cursor was updated or deleted between the
FETCH and UPDATE/DELETE...WHERE CURRENT statements and is no longer
available.
Effect. The UPDATE/DELETE WHERE CURRENT statement is invalid.
Recovery. Perform another FETCH then an UPDATE/DELETE.
8104 The operation is prevented by the check on view name1
cascaded from the check option on name2.
8105 The operation is prevented by the check option on view
name.
8106 The last row fetched by this cursor was updated or
deleted between the FETCH and UPDATE/DELETE...WHERE
CURRENT... of statements.