Global exclusions

If you use only a general, query-based method to delete objects, you can delete objects unintentionally that you need to preserve. Global exclusions help prevent this unintentional deletion.

SOAD excludes the following types of objects:

Model object types

To prevent deleting objects that are required for operating the database, SOAD excludes the object types listed in a model attribute named soadf_excluded_types.

The default set of excluded types is as follows:
model
mcomp
cvtype
attype
bstype
admin
tset
recon_temp
folder_temp

Candidate objects in excluded projects

SOAD security rules prevent any object that is used in a project from being deleted. Because the restriction is a global, the rule is applied to all scopes.

Last static versions of objects

Note: This option is applicable only if you are also using the Save Offline option.

SOAD excludes any object that is the last (static) version of that object instance. Then the user cannot create an object with the same name and type after it has been deleted, where the instance value would be reused. Restoring the original saved object is impossible because a cluster_id conflict occurs.

SOAD applies this rule by determining the depth of each version from the history root and choosing the static object with the highest depth. If the object has no static version, SOAD finds a non-static version with the highest depth, searching for a prep version first, then a version in any other state.


Feedback