Oracle公司内部数据库培训资料10约束.pptVIP

内容总结 约束。CONSTRAINT emp_emp_id_pk。[CONSTRAINT constraint_name] constraint_type。(column, ...),。CONSTRAINT emp_hire_date_nn。CONSTRAINT dept_id_pk PRIMARY KEY(department_id))。CONSTRAINT emp_salary_min。ALTER TABLE employees。DISABLE CONSTRAINT emp_emp_id_pk CASCADE。ENABLE CONSTRAINT emp_emp_id_pk。FROM user_cons_columns 第三十页，共三十页。 Schedule: Timing Topic 45 minutes Lecture 25 minutes Practice 70 minutes Total Lesson Aim In this lesson, you learn how to implement business rules by including integrity constraints. Constraints The Oracle Server uses constraints to prevent invalid data entry into tables. You can use constraints to do the following: Enforce rules on the data in a table whenever a row is inserted, updated, or deleted from that table. The constraint must be satisfied for the operation to succeed. Prevent the deletion of a table if there are dependencies from other tables Provide rules for Oracle tools, such as Oracle Developer Data Integrity Constraints  For more information, see Oracle9i SQL Reference, “CONSTRAINT.” Constraint Guidelines All constraints are stored in the data dictionary. Constraints are easy to reference if you give them a meaningful name. Constraint names must follow the standard object-naming rules. If you do not name your constraint, the Oracle server generates a name with the format SYS_Cn, where n is an integer so that the constraint name is unique. Constraints can be defined at the time of table creation or after the table has been created. You can view the constraints defined for a specific table by looking at the USER_CONSTRAINTS data dictionary table. 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 colum