|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
18/Aug/07 02:30 AM
|
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Closed
Major
Atomic operation on entries
