> 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)?
OIDs are in SQL-92(?), so we will have to keep them. I believe we may
someday make them optional on user tables.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
