Howdy, 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 Here is a patch for module/main which shows the line which needs to be removed to make this function normally (this was supposedly added to improve "postgis streaming" during reads... but this doesn't logically make any sense... perhaps it is an optimization for GeoServer?) http://jira.codehaus.org/secure/attachment/23492/UDIG-1051-main.diff Without this patch, jdbc datastores will spawn a transaction if the data is in *read-only* mode. The user should be responsible for determining if they want the transaction to be AUTO_COMMIT or not? Does anyone oppose this change? Thanks, 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
