|
From: David A. <da...@ri...> - 2005-02-02 11:58:42
|
The exception occurs with the DB2 UDB V8.2 JDBC driver. Although I haven't quite figured out the GeoTools Transaction architecture, shouldn't this address the problem? Default commit processing should probably be defined by the DataStore. At 06:25 PM 2/1/2005, Chris Holmes wrote: > > If the query to be executed does not perform a write operation, > > Query::executeQuery issues conn.setAutoCommit(false). > > > > With some JDBC providers, this causes an exception when the connection is > > closed but a commit has not performed. With the call to > > setAutoCommit(false), when the result set and statement are closed, no > > commit is performed and the subsequent attempt to close the connection > fails. > > > > Am I doing something wrong? > > > > (note: the code includes the comment "for postgis streaming, but I don't > > believe it hurts anyone" above the line where it sets autoCommit) > >Hmmm... So it is hurting someone? What jdbc provider are you using? Are >you writing a new DataStore? If needed I can figure out a way to move >that autocommit call down to postgis - I think it was just in a private >method, or a method I didn't want to override just for that one call. > >It is kind of lame that postgres needs that - for some reason if you don't >set that (and you also have to do some other random thing, fetch size less >than 50 or some such), then the driver will put everything in memory, so >that it's not actually streaming. > >Chris > > > > > > > > > > > >-- > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Geotools-gt2-users mailing list >Geo...@li... >https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users > > >-- >No virus found in this incoming message. >Checked by AVG Anti-Virus. >Version: 7.0.300 / Virus Database: 265.8.3 - Release Date: 1/31/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.3 - Release Date: 1/31/2005 |