You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2012/12/31 18:10:15 UTC

[jira] [Resolved] (ROL-1156) Add "notify intent to update" method to Roller

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

Glen Mazza resolved ROL-1156.
-----------------------------

    Resolution: Won't Fix

Unsure but I think the needs/benefit for this change has been largely reduced by time and the persistence frameworks commonly in use since 2006.  Also unsure of the need for Roller to support persistence frameworks other than the one it ships with.
                
> Add "notify intent to update" method to Roller
> ----------------------------------------------
>
>                 Key: ROL-1156
>                 URL: https://issues.apache.org/jira/browse/ROL-1156
>             Project: Roller
>          Issue Type: Improvement
>          Components: Database Access & Data Model
>            Reporter: Craig L Russell
>            Assignee: Roller Unassigned
>
> A common requirement of current persistence implementations is the requirement that before an insert, update, or delete is performed, a transaction must be started in the persistence context. JDO 1 requires a transaction for insert, update, and delete. TopLink requires registering objects in a UnitOfWork before changing them.
> JDO 2 and JPA can use lazy notification of update, via a standard feature of JPA and an optional feature of JDO (not implemented by all JDO vendors). Even implementations that support lazy notification might work better (more efficiently) if notified before changing objects. 
> So, it's a requirement that the persistence implementation be notified about the intent to update prior to instances actually being updated. Implementations that don't require notification can simply ignore the method.
> I propose a new Roller API to notify the persistence implementation that an update is intended and therefore a transaction should be started iff the implementation does not support out-of-transaction updates.
> Roller.notifyUpdateIntent() would work. Roller.beginUnitOfWork would work. The updateIntent state would be ended by flush or release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira