Skip site navigation (1) Skip section navigation (2)

Re: Complexity of contrib types

From: Hannu Krosing <hannu(at)trust(dot)ee>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Complexity of contrib types
Date: 1998-07-21 16:02:40
Message-ID: 35B4BBA0.44E66103@trust.ee (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian wrote:
> 
> 
> We could create a function that returned the previously inserted oid,
> and use that in the next query.
> 
>         insert into test values (4);
>         update test3 set val = lastoid();
> 
> Just remember the lastoid inserted in the backend code.  Seems easy.  Do
> you want it added to the TODO list.

Yes. It could be used in several places.

But I'm currently not aware about the future of oid's 'at the large'. 

I have understood that we are on a way of getting rid of OIDs for 
non-system tables (and having to re-implement them using triggers 
and sequences where/when needed)?

Hannu

In response to

Responses

pgsql-hackers by date

Next:From: D'Arcy J.M. CainDate: 1998-07-21 16:07:32
Subject: Re: [HACKERS] cidr
Previous:From: Bruce TongDate: 1998-07-21 15:51:23
Subject: Re: [GENERAL] Re: [HACKERS] [Fwd: SGVLLUG Oracle and Informix on Linux]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group