DatabaseHandle :: SetVersioningMode - Set versioning mode

The function sets the versioning mode of the database to the value passed in eVersioningMode. After changing the versioning mode, the database has to be re-opened. In general, the versioning mode cannot be changed after being set. Some exceptions (feature downgrade) are, however, accepted:

• database --> synchronized --> not synchronized (consistency feature)
• database --> objectspace --> owner --> instance (scope feature)
• managed... --> not managed... (level feature)

Other transitions are not allowed and will cause an exception. Especially, pure managed versioning mode (old schema databases) cannot be changed without copying the database, when major versions have already been created.

As long as there are no versions created for database entries or the database or object space, version modes may be change without restrictions.

Changing the versioning mode affects database access. After calling the function, selections in all property handles will be reset and instances have to be relocated. The access version is set to the current version, which is usually the last version created.