Ned Wolpert [EMAIL PROTECTED] 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 ...
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
Ugh... a quick search shows me asking this same thing in May, when the 'big
TODO' list was being
Ned Wolpert [EMAIL PROTECTED] writes:
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?
Yech. At least, not with *that* syntax. @@ is a valid operator name
in Postgres.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, so you're not opposed to the idea then, just the syntax. Does anyone
oppose having this concept in the JDBC driver? And what syntax is acceptable?
Could we just do
'select getInsertedOID()'
which would break people who have functions called
