>I have a suggestion...
>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.
With a default to return the primary key?
Joshua D. Drake
>---------------------------(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
Description: text/x-vcard (285 bytes)
In response to
pgsql-novice by date
|Next:||From: Neil Conway||Date: 2005-02-01 22:44:47|
|Subject: Re: [NOVICE] Last ID Problem|
|Previous:||From: Tom Lane||Date: 2005-02-01 16:08:27|
|Subject: Re: [NOVICE] Last ID Problem |
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2005-02-01 17:06:30|
|Subject: Re: float4 regression test failed on linux parisc |
|Previous:||From: Tom Lane||Date: 2005-02-01 16:54:55|
|Subject: Re: STABLE functions |