-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What about the 'select @@last_oid' to make the getInsertedOID() call available
even when the driver is wrapped by a pooling manager?
How do people feel about this? (I would be happy to contribute to the codebase
for this one.) I understand the RETURNING clause is more work... and I would
like to help out on that for 7.3.
On 21-Aug-2001 Tom Lane wrote:
> Ned Wolpert <ned.wolpert@knowledgenet.com> writes:
>> 1) Being able to use the RETURNING clause in prepared statements, like
>> this
>> "INSERT INTO tableName (key1,...)
>> VALUES (value1,...)
>> RETURNING primKeyName INTO ?"
>> Which is what Oracle provides.
>
> INSERT ... RETURNING was discussed recently, and I think people agreed
> it's a good idea, but it got hung up on some unresolved issues about how
> it should interact with ON INSERT rules for views. Search the pghackers
> mailing list archives for details. At this point I think it's probably
> too late to consider it for 7.2, but I'm still open to doing it in 7.3
> if we can come up with a bulletproof spec.
>
> regards, tom lane
Virtually,
Ned Wolpert <ned.wolpert@knowledgenet.com>
D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7gtIoiysnOdCML0URAmgIAJwJVf2BGhFq88bXHY3yni9qzGohegCdHmPf
7Xnb57gfiP2xoMC8x5mIhWU=
=p5Bx
-----END PGP SIGNATURE-----