Data exceptions  Invalid cursor states

Chapter 6: SQLSTATE Codes and Messages

Integrity constraint violations

Integrity constraint violations occur when an insert, update, or delete statement violates a primary key, foreign key, check, or unique constraint or a unique index.

Table 6-4: Integrity constraint violations

Message

Value

Description

Attempt to insert duplicate key row in object object_name with unique index index_name.

23000

Occurs when a duplicate row is inserted into a table that has a unique constraint or index.

Check constraint violation occurred, dbname = database_name, table name = table_name, constraint name = constraint_name.

23000

Occurs when an update or delete would violate a check constraint on a column.

Dependent foreign key constraint violation in a referential integrity constraint. dbname = database_name, table name = table_name, constraint name = constraint_name.

23000

Occurs when an update or delete on a primary key table would violate a foreign key constraint.

Foreign key constraint violation occurred, dbname = database_name, table name = table_name, constraint name = constraint_name.

23000

Occurs when an insert or update on a foreign key table is performed without a matching value in the primary key table.





Copyright © 2005. Sybase Inc. All rights reserved. Invalid cursor states

View this book as PDF