Re: question about constraint
From: <msabbey_at_magi.com>
Date: 1996/04/28
Message-ID: <4luis2$mkk_at_news.magi.com>#1/1
Date: 1996/04/28
Message-ID: <4luis2$mkk_at_news.magi.com>#1/1
Some people prefer doing it this way - when a row is created or updated to a NULL value, the error message can be more descriptive to the user. Also, with a named column constraint, the developer can more easily zero in on the offending portion of code in an application knowing a constraint name.
Michael
duffy_at_cais2.cais.com (MCC) wrote:
>What is the purpose of having a CONSTRAINT in the following statement:
> CREATE TABLE s_ord
> (id NUMBER(7),
> customer_id NUMBER(7)
> CONSTRAINT s_ord_customer_id nn NOT NULL,
> .
> .
> .
> );
> why can't we just define customer_id to NUMBER(7) NOT NULL?
>Thanks,
>Duffy
Received on Sun Apr 28 1996 - 00:00:00 CEST