|
If you were logged in you would be able to see more operations.
|
|
|
| Proposal: |
I don't think we need to add this... but wanted to give the TC a chance to think about it.
|
| Resolution: |
We won't add in a parameter, but we will clarify that if the repository fails to delete one or more versions, it must leave the version series in a valid state.
|
|
Currently, there are 2 CMIS methods that attempt to delete >1 object at a time.
- DeleteTree: Deletes all objects in a folder tree.
- DeleteAllVersions: Deletes all documents in a folder series.
DeleteTree includes semantics/parameters for how the Repository should behave if for any reason it CANNOT delete one of the objects in the Folder Tree.
Should we add the same semantics for DeleteAllVersions?
|
|
Description
|
Currently, there are 2 CMIS methods that attempt to delete >1 object at a time.
- DeleteTree: Deletes all objects in a folder tree.
- DeleteAllVersions: Deletes all documents in a folder series.
DeleteTree includes semantics/parameters for how the Repository should behave if for any reason it CANNOT delete one of the objects in the Folder Tree.
Should we add the same semantics for DeleteAllVersions? |
Show » |
|
Bug
Closed
Major
Should "deleteAllVersions" have "continueOnFailure" semantics like "DeleteTree" does?
But DeleteAllVersions can probably more easily do this in an all-or-nothing manner (including the PWC) so I'm for saying that it MUST delete nothing if there's an error.