Re: A basic Statement.getGeneratedKeys() implementation (patch attached)

Kris Jurka wrote: <blockquote cite="mid:Pine.BSO.4.64.0905011649310.13271@leary.csoft.net" type="cite"><br /><br /> On
Fri,1 May 2009, Adam B wrote: <br /><br /><blockquote type="cite">Our webapp relies heavily on JDBC's
Statement.getGeneratedKeys()<br /> abstraction.  We are investigating switching from Mysql to Postgre so I <br />
createda basic implementation of this feature in the 8.3-604 version of <br /> the driver.  The diff patch is attached.
<br/></blockquote><br /> This has some pretty severe restrictions and some more that aren't mentioned (overriding
getUpdateCount(),not using the V2 protocol which has nothing to do with JDBC2/3).  We've implemented generated key
supportin CVS for the upcoming 8.4 release that is more robust, but makes some other tradeoffs (returning all columns
ratherthat just a single key).  Could you test this out in your application? <br /></blockquote> I'd be glad to give
thata try.  I'm all for an official implementation as long as it's reasonably fast.  However I probably wont be able to
getto it for about a week (vacation).<br /><blockquote cite="mid:Pine.BSO.4.64.0905011649310.13271@leary.csoft.net"
type="cite"><br/> CVS info here: <br /><br /><a class="moz-txt-link-freetext"
href="http://jdbc.postgresql.org/development/cvs.html">http://jdbc.postgresql.org/development/cvs.html</a><br/><br /> A
threaddiscussing how it doesn't work for a Spring application here: <br /><br /><a class="moz-txt-link-freetext"
href="http://archives.postgresql.org//pgsql-jdbc/2009-04/threads.php#00081">http://archives.postgresql.org//pgsql-jdbc/2009-04/threads.php#00081</a><br
/><br/> Kris Jurka <br /></blockquote><br /><br /><br /><hr />
Videx Inc. 1105 N. E. Circle Blvd. Corvallis OR 97330 (541) 758-0521<br/>
CONFIDENTIAL COMMUNICATION: The email message and any attachments are intended only for the addressee.  They may be privileged, confidential, and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying is expressly prohibited.  If you received this email message in error, please notify the sender immediately by replying to this e-mail message or by telephone<br
/>