Please ignore that email. I was totally lost in what I was trying to
understand from the them. The trigger is for something else..
Sorry for the trouble.
BTW... The decision is to upgrade to 8i and use IOT..
> -----Original Message-----
> From: Deshpande, Kirti
> Sent: Thursday, August 31, 2000 2:21 PM
> To: 'oracle list'
> Subject: Enforcing Uniqueness
>
> Hello listers,
> We are discussing with some developers as to what is the best way to
> enforce unique constraint on some of the tables in one particular
> application. I thought I would ask you all for your opinion as well.
> Some of these tables have just one or two columns (sort of look up or
> reference tables). All column data must be unique. What would make more
> sense : (a) have a before insert trigger or (b) create regular PK
> constraint using an index. There are no other RI on theses tables. We will
> consider IOT when we go to oracle 8.x. Currently these are in a 7.3.4 db.
> These tables have less than 2000 rows.. less than 2% growth per year.
> So what would you suggest? A Trigger or a PK constraint. What are the
> pros and cons?
> Thanks..
Received on Thu Aug 31 2000 - 14:33:29 CDT
