On Thu, May 03, 2007 at 10:58:38AM +1200, Brent Wood wrote:
> As oid is unique across all tables (in fact all database objects), but
> serial is unique within a table, there are odd cases like this where
> using an oid in each table ensures an automatic unique key in the view.
> So oids can be u
On May 2, 2007, at 3:58 PM, Brent Wood wrote:
Richard Huxton wrote:
OIDs are used by the various system tables.
Historically, all user tables had them too.
There's no reason to use them in a new system - they offer no
advantages over an ordinary integer primary-key.
Generally this is cor
Richard Huxton wrote:
Jasbinder Singh Bali wrote:
Hi,
What would be the benefit of creating tables with OIDs as against
one's not
with OIDs
Giving a unique identifier to each row inserted has some extra
efficiency
factor involved or what.
OIDs are used by the various system tables.
Histor
Jasbinder Singh Bali wrote:
Hi,
What would be the benefit of creating tables with OIDs as against one's not
with OIDs
Giving a unique identifier to each row inserted has some extra efficiency
factor involved or what.
OIDs are used by the various system tables.
Historically, all user tables had
Hi,
What would be the benefit of creating tables with OIDs as against one's not
with OIDs
Giving a unique identifier to each row inserted has some extra efficiency
factor involved or what.
Thanks,
Jas
