Controls the range of updates that are permitted.
Sybase IQ provides several extensions that allow updates that are not permitted by the ANSI SQL standard. These extensions provide powerful, efficient mechanisms for performing updates. However, in some cases, they cause behavior that is not intuitive. This behavior might produce anomalies such as lost updates if the user application is not designed to expect the behavior of these extensions.
ANSI_UPDATE_CONSTRAINTS controls whether updates are restricted to those permitted by the SQL92 standard.
If the option is set to STRICT, these updates are prevented:
Updates of cursors containing JOINS
Updates of columns that appear in an ORDER BY clause
The FROM clause is not allowed in UPDATE statements.
If the option is set to CURSORS, these same restrictions are in place, but only for cursors. If a cursor is not opened with FOR UPDATE or FOR READ ONLY, the database server determines whether updates are permitted based on the SQL92 standard.
If ANSI_UPDATE_CONSTRAINTS is set to CURSORS or STRICT, cursors containing an ORDER BY clause default to FOR READ ONLY; otherwise, they continue to default to FOR UPDATE.
This code has a different effect, depending on the setting of ANSI_UPDATE_CONSTRAINTS:
CREATE TABLE mmg (a CHAR(3)); CREATE TABLE mmg1 (b CHAR(3));
INSERT INTO mmg VALUES ('001');
INSERT INTO mmg VALUES ('002');
INSERT INTO mmg VALUES ('003')
INSERT INTO mmg1 VALUES ('003');
SELECT * FROM mmg;
SELECT * FROM mmg1;
Option 1: Set ANSI_UPDATE_CONSTRAINTS to STRICT:
SET OPTION public.Ansi_update_constraints = 'strict'; DELETE MMG FROM MMG1 WHERE A=B;
This results in an error indicating that the attempted update operation is not allowed.
Option 2: Set ANSI_UPDATE_CONSTRAINTS to CURSORS or OFF:
SET OPTION public.Ansi_update_constraints = 'CURSORS'; // or 'OFF' DELETE mmg FROM mmg1 WHERE A=B;
In this case, the deletion should complete without the error.