Oracel_Les10_chinese 约束.pptVIP

Defining Constraints The slide gives the syntax for defining constraints while creating a table. In the syntax: schema is the same as the owner’s name table is the name of the table DEFAULT expr specifies a default value to use if a value is omitted in the INSERT statement column is the name of the column datatype is the column’s data type and length column_constraint is an integrity constraint as part of the column definition table_constraint is an integrity constraint as part of the table definition For more information, see Oracle9i SQL Reference, “CREATE TABLE.” Defining Constraints (continued) Constraints are usually created at the same time as the table. Constraints can be added to a table after its creation and also temporarily disabled. Constraints can be defined at one of two levels. In the syntax: constraint_name is the name of the constraint constraint_type is the type of the constraint Instructor Note Explain that the column level and the table level refer to location in the syntax. The NOT NULL Constraint The NOT NULL constraint ensures that the column contains no null values. Columns without the NOT NULL constraint can contain null values by default. The NOT NULL Constraint (continued) The NOT NULL constraint can be specified only at the column level, not at the table level. The slide example applies the NOT NULL constraint to the LAST_NAME and HIRE_DATE columns of the EMPLOYEES table. Because these constraints are unnamed, the Oracle server creates names for them. You can specify the name of the constraint when you specify the constraint: ... last_name VARCHAR2(25) CONSTRAINT emp_last_name_nn NOT NULL... Note: The constraint examples described in this lesson may not be present in the sample tables provided with the course. If desired, these constraints can be added to the tables. The UNIQUE Constraint A UNIQUE key integrity constraint requires that every value in a column or set of columns (key) be unique—tha