Cory Horner wrote: >We're changing the way uDig uses transactions -- so a transaction is >AUTO_COMMIT until a modification occurs, and it remains open until the >user commits the transaction: > >http://jira.codehaus.org/browse/UDIG-1051 > > On second though, this does seem to be needed for PostGIS. If a transaction is not present during a read, it cannot be canceled mid-collection using our current strategy. The override of this method should be moved into PostGIS, rather than module/main (the original comment read something along the lines of "this is for PostGIS, but it probably doesn't hurt anyone else").
We do need to still do some testing however, to ensure that the transaction goes like this: Transaction=AUTO_COMMIT read features: START TRANSACTION ... SELECT * ... done: ROLLBACK; (seems strange) Transaction=AUTO_COMMIT and a read during an edit: Transation is in progress read features: ... SELECT * ... done: do nothing and keep transaction open Thoughts? Cory. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
