Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: user_constraint columns

Re: user_constraint columns

From: PaulCinVT <paulcinvt_at_aol.com>
Date: 16 Aug 1999 17:18:00 GMT
Message-ID: <19990816131800.15205.00000499@ngol07.aol.com>


DEFERRABLE
 indicates that constraint checking can be deferred until the end of the transaction by using the SET CONSTRAINT(S) command.  

NOT DEFERRABLE
 indicates that this constraint is checked at the end of each DML statement. You cannot defer a NOT DEFERRABLE constraint with the SET CONSTRAINT(S) command. If you do not specify DEFERRABLE or NOT DEFERRABLE, then NOT DEFERRABLE is the default. See also "DEFERRABLE Constraints".    

 INITIALLY IMMEDIATE
 indicates that at the start of every transaction, the default is to check this constraint at the end of every DML statement. If no INITIALLY clause is specified, INITIALLY IMMEDIATE is the default.    

 INITIALLY DEFERRED
 implies that this constraint is DEFERRABLE and specifies that, by default, the constraint is checked only at the end of each transaction.  

ENABLE VALIDATE
 ensures that all new insert, delete, and update operations on the constrained data comply with the constraint. Checks that all old data also obeys the constraint. An enabled and validated constraint guarantees that all data is and will continue to be valid. This is the default.  

ENABLE NOVALIDATE
 ensures that all new insert, update, and delete operations on the constrained data comply with the constraint. Oracle does not verify that existing data in the table complies with the constraint.  

Paul in VT Received on Mon Aug 16 1999 - 12:18:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US