db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric SULTAN (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-610) Support Nested Transaction or savePoint in JDO 2.3
Date Mon, 10 Nov 2008 20:37:44 GMT

    [ https://issues.apache.org/jira/browse/JDO-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646356#action_12646356

Eric SULTAN commented on JDO-610:

I see this feature in the kodo implementation. And it seems quite useful to have in JDO.
They use setSavepoint, releaseSavepoint and rollbackToSavepoint as you describe.

The best way in to use the setSavepoint of the the jdbc driver when it's available.
If it's not available to the target database, save all StateManager during the transaction
and tag them when they are enlisted in a savepoint.

But, I don't know how to manage this savepoint in a global transaction manager (jta).

> Support Nested Transaction or savePoint in JDO 2.3
> --------------------------------------------------
>                 Key: JDO-610
>                 URL: https://issues.apache.org/jira/browse/JDO-610
>             Project: JDO
>          Issue Type: Wish
>            Reporter: Eric SULTAN
>             Fix For: JDO 2 maintenance release 3
> It would be very usefull if the next maintenance release of JDO allow nested transaction
or savePoint if the RDBMS can do it.

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

View raw message