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
>
>
>
>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