Should "deleteAllVersions" have "continueOnFailure" semantics like "DeleteTree" does?

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      I don't think we need to add this... but wanted to give the TC a chance to think about it.

      Show
      I don't think we need to add this... but wanted to give the TC a chance to think about it.
    • Hide

      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.

      Show
      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?

            Assignee:
            Ethan Gur-esh (Inactive)
            Reporter:
            Ethan Gur-esh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: