From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | wagner(at)imsd(dot)uni-mainz(dot)de, pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: using OID as primary key |
Date: | 2000-07-21 13:58:15 |
Message-ID: | m13FdJf-000AXVC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Thus spake Jan Wieck
> > are there any disadvantages of using OID as the primary key for any
> > table?
> > What about referencing external tuples using their OIDs?
>
> Currently OID is not supported for references. Has to do with
> some checks done in the RI triggers, using SPI functions.
> We're thinking about a solution...
Also, don't forget about the dump/restore issue. You have to remember
to dump OIDs with "-o" or else all your references will be trashed.
<OPINION>
Personally I would avoid it. Adding a serial type almost gives you
the same thing anyway. OIDs are useful in system tables and temporarily
in programs when dealing with tables without primary keys.
</OPINION>
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-07-21 14:27:07 | Re: problem with view and case - please help |
Previous Message | Jan Wieck | 2000-07-21 11:57:17 | Re: using OID as primary key |