You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/08/18 02:18:31 UTC

[jira] Assigned: (DIRSERVER-684) Atomic operation on entries

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

Alex Karasulu reassigned DIRSERVER-684:
---------------------------------------

    Assignee: Alex Karasulu

> Atomic operation on entries
> ---------------------------
>
>                 Key: DIRSERVER-684
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-684
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Assignee: Alex Karasulu
>             Fix For: 1.5.1
>
>
> When applying a modification on an entry, the resulting entry should be stored in the backend only once. 
> What we have now is a double modification :
>  - modification of attributes
>  - modification of the operationnal attributes (modifytimestamp, modifiersname)
> If we have any problem between those two operations, then the entry will remain in an inconsistant state. The entry should be commited as an atomic operation, at the end of the operation.

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