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

Re: [NOVICE] Last ID Problem

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
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 16:56:52
Message-ID: 41FFB4D4.4060801@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-novice
>
>
>
>I have a suggestion...
>
>For libpq:
>
>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?
>
>This way, you could have a funtion to fetch an arbitrary named 
>column from that tuple.
>Like: last_insert_value(tuple,'column_name')
>  
>

With a default to return the primary key?

Sincerely,

Joshua D. Drake



>... John
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>  
>


-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Attachment: jd.vcf
Description: text/x-vcard (285 bytes)

In response to

Responses

pgsql-novice by date

Next:From: Neil ConwayDate: 2005-02-01 22:44:47
Subject: Re: [NOVICE] Last ID Problem
Previous:From: Tom LaneDate: 2005-02-01 16:08:27
Subject: Re: [NOVICE] Last ID Problem

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-02-01 17:06:30
Subject: Re: float4 regression test failed on linux parisc
Previous:From: Tom LaneDate: 2005-02-01 16:54:55
Subject: Re: STABLE functions

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