cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikita Timofeev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAY-2186) MySQL and Derby PK generators should not commit explicitly
Date Mon, 20 Feb 2017 09:11:44 GMT

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

Nikita Timofeev commented on CAY-2186:
--------------------------------------

Per https://github.com/stariy95/cayenne/commit/72aa17ac8f5381c18e94d3414eb2e19683857ebd DerbyPkGenerator
switched to sequence-based PK generator, which is free of this issue.


> 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.15#6346)

Mime
View raw message