Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> How is what you're suggesting more portable?
Well, the driver would be free to implement $sth->last_insert_id() using
whatever proprietary extensions it has available. The non-portableness would
at least be hidden in the driver layer. Switch out the driver and the right
thing would happen.
"INSERT/UPDATE ... RETURNING" isn't something a driver can take advantage of.
It would require it to modify your statements which it can't do safely. So
your application would have such non-portable SQL code written into it. Switch
databases and your application code needs to be ported.
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2005-02-02 17:00:05|
|Subject: Re: [BUGS] Bug in create operator and/or initdb|
|Previous:||From: Martin Pitt||Date: 2005-02-02 16:53:59|
|Subject: Re: libpq API incompatibility between 7.4 and 8.0|