Operations on Versioned Objects

OPM supports operations on both versioned and non-versioned objects. Operations for non-versioned objects include insertion, deletion and update. Operations for versioned objects and individual versions are:

1. create new version: new versions can be created from old versions of existing objects, or for new objects;

2. logical delete: a version can be marked as logically deleted; a version still exists in the database after logical deletion;

3. restore or logical undelete: a logically deleted version can be restored by removing the logical delete mark;

4. physical delete: a versioned object and/or each individual version can be physically deleted from the database; after the physical deletion, the data are removed from the database, and cannot be restored;

5. copy: a new version is created by copying an existing version that is not marked as logically deleted;

6. update: an existing version can be updated in place; that is, attribute values of the existing version are replaced by the new values; no new version is created; in order to create a new version, a user can first create a new version by copying this version, and then perform the update on the new version;

7. set default: a version can be selected to be the current default version of an object.