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

Privilege and Alias Messages (1000 through 1999)
HP NonStop SQL/MX Messages Manual—523730-004
3-13
SQL 1049
Cause. You attempted to drop a constraint that is NOT DROPPABLE.
Effect. The operation fails.
Recovery. None.
SQL 1050
Cause. You attempted to drop a unique or primary constraint, with dependent
referential constraints, using the RESTRICT option, which does not remove such
constraints.
Effect. The drop command fails.
Recovery. If you want to drop the dependent referential constraints, use the
CASCADE option for the DROP CONSTRAINT command.
SQL 1051
Where object-name is the name of the object for which you have insufficient
privileges.
Cause. You have insufficient privileges to create a view or a trigger.
Effect. The operation fails.
Recovery. See the SQL/MX Reference Manual for the required security needed to
create a view or trigger.
SQL 1052
Cause. An ALTER TABLE statement with DROP CONSTRAINT specified a name that
is not the name of a constraint on this table.
Effect. No constraint is dropped.
1049 Constraint cannot be dropped because it was specified to
be NOT DROPPABLE.
1050 Constraint cannot be dropped because it is used as a
referenced object for a foreign key.
1051 You do not have the required privilege(s) on object-
name.
1052 Constraint cannot be dropped because it does not belong
to the specified table.