From: | Kostis Mentzelos <mentzelos(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OID's |
Date: | 2004-11-16 11:06:57 |
Message-ID: | cncn0v$29ob$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Glaesemann wrote:
>
> On Nov 15, 2004, at 3:52 PM, Jamie Deppeler wrote:
>
>> Hi,
>>
>> I am planning to use OID for referencing as instead PK -->> FK on
>> this situation would require alot of tables, OID would seen to nice
>> solution.
>>
>> My worry with OID's is when i do SQL dump and rebuild the Database
>> will OID will change making referencing certain records impossible.
>
>
> Don't use OIDS. Just add a nice SERIAL column to the tables you want as
> foreign keys (and if you have questions about sequences, check the FAQ).
>
> OIDS are a system level implementation. They are no longer required (you
> can make tables without OIDS) and they may go away someday. Plus, you
> avoid nastiness like OID wraparound.
>
> Michael Glaesemann
> grzm myrealbox com
>
> (Is it just me, or have there been a slew of these OID posts lately?)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
I have read about oid wraparound in many messages but I don't understand
when it happens and when it is dangerus for my tables.
It affects developers that uses OIDS in their queryies?
What about database and tables (not total or total) disappearences?
Kostis.
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Rylander | 2004-11-16 11:28:47 | Re: How the function written on pl/pgsql can be called by the function written on plperl. |
Previous Message | Neil Conway | 2004-11-16 10:53:42 | Re: OID's |