[ 
https://issues.apache.org/jira/browse/DERBY-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lily Wei updated DERBY-4314:
----------------------------

    Attachment: DERBY-4314-7b-combine.diff

Thanks Kristian for combined patch with some additional XA changes in the 
client. I believe the fix also address the server does not send any 
piggybacking update and improve the performance concern since we are getting 
the right isolation level. We still need to think about whether to check 
isolation_ value to TRANSACTION_READ_COMMITTED. With this patch, I also add 
more comment on setTransactionIsolation since that was why we commit when call 
setTransactionIsolation. 

Suite.all and derby tests passed.

> With derby client setTransactionIsolation executes and commits even if 
> isolation has not changed 
> -------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4314
>                 URL: https://issues.apache.org/jira/browse/DERBY-4314
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>    Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1, 
> 10.6.1.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: DERBY-4314-2.diff, DERBY-4314-3.diff, DERBY-4314-5.diff, 
> derby-4314-6a-initial_piggybacking.diff, 
> derby-4314-6a-initial_piggybacking.stat, 
> DERBY-4314-6b-combinepiggybacking.diff, DERBY-4314-6c-combineaftermerge.diff, 
> derby-4314-6d-handle_xa.diff, DERBY-4314-7-withoutpiggybacking.diff, 
> DERBY-4314-7b-combine.diff, DERBY-4314.diff, ReproIsoLost.java, 
> TestConnReuse.java, utilXid.java
>
>
> With in EmbedConnection.setIsolation() we have a check to see if the 
> isolation level is the same and if so just return without doing a commit:
>   public void setTransactionIsolation(int level) throws SQLException {
>               if (level == getTransactionIsolation())
>                       return;
> with org.apache.derby.client.am.Connection we have no such check. It would be 
> good if the client driver acted like embedded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to