(mysql.info.gz) constraint primary key

Info Catalog

(mysql.info.gz) Constraints

(mysql.info.gz) Constraints

(mysql.info.gz) constraint invalid data

 
 1.5.6.1 `PRIMARY KEY' and `UNIQUE' Index Constraints
 ....................................................
 
 Normally, an error occurs when you try to `INSERT' or `UPDATE' a row
 that causes a primary key, unique key, or foreign key violation.  If
 you are using a transactional storage engine such as `InnoDB', MySQL
 automatically rolls back the statement.  If you are using a
 non-transactional storage engine, MySQL stops processing the statement
 at the row for which the error occurred and leaves any remaining rows
 unprocessed.
 
 If you wish to ignore such key violations, MySQL supports an `IGNORE'
 keyword for `INSERT' and `UPDATE'. In this case, MySQL ignores any key
 violations and continues processing with the next row.   `INSERT'
 INSERT.   `UPDATE' UPDATE.
 
 You can get information about the number of rows actually inserted or
 updated with the `mysql_info()' C API function.   `mysql_info()'
 mysql_info.  In MySQL 4.1 and up, you also can use the `SHOW WARNINGS'
 statement.   `SHOW WARNINGS' SHOW WARNINGS.
 
 For the moment, only `InnoDB' tables support foreign keys.  
 InnoDB foreign key constraints.  Foreign key support in `MyISAM'
 tables is scheduled for implementation in MySQL 5.1.
 

Info Catalog

(mysql.info.gz) Constraints

(mysql.info.gz) Constraints

(mysql.info.gz) constraint invalid data