[ http://issues.apache.org/jira/browse/DERBY-2060?page=comments#action_12454110 ] Kim Haase commented on DERBY-2060: ----------------------------------
Actually the question is a little broader than that, because there's a matrix of four situations -- Network client driver or embedded driver SET ISOLATION statement or Connection.setTransactionIsolation method I gather you're saying there is a difference in behavior among these if you set the isolation level to its current value (i.e. you don't change it)? Do the statement and method both go ahead and commit the transaction anyway, *except* if you are using the Connection.setTransactionIsolation method with the embedded driver? Thanks very much. > SET CURRENT ISOLATION in ref.man refers > java.sql.Connection.setTransactionLevel instead of > java.sql.Connection.setTransactionIsolation > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2060 > URL: http://issues.apache.org/jira/browse/DERBY-2060 > Project: Derby > Issue Type: Bug > Components: Documentation > Reporter: Bernt M. Johnsen > Assigned To: Kim Haase > Attachments: DERBY-2060.diff, DERBY-2060.zip > > > On SET CURRENT ISOLATION statement in the Derby refernce manual: > "Issuing this command commits the current transaction, which is consistent > with the java.sql.Connection.setTransactionLevel method." > The correct method name is java.sql.Connection.setTransactionIsolation > (java.sql.Connection.setTransactionLevel does not exist) > BTW: setTransactionIsolation will commit the current transaction if called in > the client driver but not in the embedded driver. See DERBY-638 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
