RE: non unique Index and Primary Key on same column. Is it needed?
- From: "Jacques Kilchoer" <Jacques.Kilchoer@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 25 Aug 2004 09:59:58 -0700
I've seen plenty of schemae where there wasn't a separate not null
constraint on the primary key columns. The thinking is that the PK
constraints enforces the "not null" so a separate one isn't needed.
When I was a developer, I used to do that until a DBA convinced me that
it wasn't a good idea.
-----Original Message-----
Mark W. Farnham
null values in pk columns? ain't it sorta a schema design error to have
nullable columns as components of the pk?
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
