From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | hannu(at)trust(dot)ee (Hannu Krosing) |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Complexity of contrib types |
Date: | 1998-07-21 16:36:08 |
Message-ID: | 199807211636.MAA00440@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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)?
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(at)candle(dot)pha(dot)pa(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1998-07-21 16:37:42 | Re: [HACKERS] next XID is in shmem now... |
Previous Message | Thomas G. Lockhart | 1998-07-21 16:33:47 | Re: Linux Oracle! (fwd) |