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

Re: [NOVICE] Last ID Problem

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: John Hansen <john(at)geeknet(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Fuhr <mike(at)fuhr(dot)org>,Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com>,Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org,operationsengineer1(at)yahoo(dot)com, pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Last ID Problem
Date: 2005-02-01 14:24:38
Message-ID: 20050201142438.GC5069@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-novice 
On Tue, Feb 01, 2005 at 06:31:30PM +1100, John Hansen wrote:

> Since OID's are now deprecated, and will eventually disappear,
> wouldn't it be a good idea, to have INSERT and UPDATE return 
> a copy of the tuple that was inserted/updated?

How about the TID?

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"El destino baraja y nosotros jugamos" (A. Schopenhauer)

In response to

Responses

pgsql-novice by date

Next:From: John HansenDate: 2005-02-01 14:48:49
Subject: Re: [NOVICE] Last ID Problem
Previous:From: Kjetil HaalandDate: 2005-02-01 14:19:23
Subject: Re: function returning a row

pgsql-hackers by date

Next:From: John HansenDate: 2005-02-01 14:48:49
Subject: Re: [NOVICE] Last ID Problem
Previous:From: a_ogawaDate: 2005-02-01 13:06:43
Subject: Re: FunctionCallN improvement.

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