Hi, > Now I'm using LinkedTable objects under following conditions : > ACCESS_MODE=R > OPEN_NEW=TRUE > SHARE_LINKED_CONNECTIONS=TRUE > > When I issue SELECT statement which use JOIN clause, > SQLException is thrown because ResultSet is closed under > the condition. > > the JDBC I use seems to close all ResultSets when one > of them which share the same connection is read completely > on auto commit mode even though H2 is still working on other > ResultSets(because ShareLinkedConnections functionality). > > So, I want to set auto commit mode off for the connetcions > which LinkedTable objects use internally.
I'm not sure what are the side effects of switching off autocommit. What database do you use? > Are there any idea to customise(ie. set auto commit off) JDBC > connections used by LinkedTable? Currently the only customization is switching off shared connections. In your case that would work I think. Would that work? > I come up with preparing jdbc driver wrapper for the JDBC and > return connection object with auto commit off to H2 Database > Engine, but it is a little bit awkward. I agree. Of course I could add a setting to switch off auto commit if that solves the problem. Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
