Difference between revisions of "SQL Constraints"
From Lianjapedia
Yvonne.milne (Talk | contribs) (→Column Constraints) |
Yvonne.milne (Talk | contribs) (→Column Constraints) |
||
Line 47: | Line 47: | ||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
|[[AUTO_INCREMENT Column Constraint|AUTO_INCREMENT]] | |[[AUTO_INCREMENT Column Constraint|AUTO_INCREMENT]] | ||
+ | |- | ||
+ | |[[AUTOSUGGESTIONS Column Constraint|AUTOSUGGESTIONS]] | ||
+ | |- | ||
+ | |[[AUTOSUGGESTIONHEADERS Column Constraint|AUTOSUGGESTIONHEADERS]] | ||
|- | |- | ||
|[[AUTOINC Column Constraint|AUTOINC]] | |[[AUTOINC Column Constraint|AUTOINC]] |
Revision as of 05:06, 27 March 2018
Purpose
To define rules that help to provide data integrity
See Also
ALTER TABLE, CREATE TABLE, GRANT, REVOKE
Description
A constraint is used to define rules that help to provide data integrity. There are two different types of constraints, TABLE constraints, which do not require any column information and column constraints, which are specific to the column name specified. You must have ALTER privilege on the table. The table will be locked for EXCLUSIVE use during the operation.
Table Constraints
CHECK |
ERROR |
FOREIGN KEY |
INDEX |
KEY |
ONAFTERDELETE |
ONAFTERINSERT |
ONAFTERUPDATE |
ONCLOSE |
ONBEFOREDELETE / ONDELETE |
ONBEFOREINSERT / ONINSERT |
ONOPEN |
ONBEFOREUPDATE / ONUPDATE |
PRIMARY KEY |
UNIQUE |