[jira] [Commented] (CAY-2186) MySQL and Derby PK generators should not commit explicitly

["Andrus Adamchik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAY-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15792947#comment-15792947 ] 

Andrus Adamchik commented on CAY-2186:
--------------------------------------

TODO: check with a real JTA transaction manager (e.g. https://github.com/bitronix/btm ) . Cause testing without one does not present the correct connection state (e.g. ExternalTransaction will not flip autoCommit to false), so it is hard to make proper assertions.

> MySQL and Derby PK generators should not commit explicitly
> ----------------------------------------------------------
>
>                 Key: CAY-2186
>                 URL: https://issues.apache.org/jira/browse/CAY-2186
>             Project: Cayenne
>          Issue Type: Bug
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>            Priority: Minor
>
> MySQL and Derby PK generators explicitly commit the connection when they get a new PK. This goes against Cayenne strategy for *external* transaction management (do not commit from inside Cayenne, let the transaction manager commit when needed). 
> Haven't tested the behavior with a real tx manager, but without one (and with external transactions) these 2 PK generators add a side effect of committing whatever else was uncommitted on the connection in question.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)