Properties assigned to DCM objects

All objects in a DCM database are automatically assigned special properties. Some of these properties are: Local To, From, Modifiable In, and Work in DB. DCM uses these traits to preserve the uniqueness and histories of all objects in a DCM cluster. The properties are described as follows:

The value of the Local To property (the local_to attribute) is the database ID of the database in which the object is either initialized or created. The Local To value remains with all versions of an object. It never changes during the entire history of the object. All successors of a DCM object inherit its Local To value regardless of where the new versions are checked out.

The value of the From property (the created_in attribute) is the ID of the database from which the object version is checked out. The From value is assigned only to a particular version; it is not inherited by successors.

Note: When an object is created (by a user or during DCM initialization), the value of the From property is set to the ID of the database in which it is created. Thus, the Local To and From values are always identical for the first version of a DCM object.

Modifiable In or Work in DB - The value of the Modifiable In property (the modifiable_in attribute) is the ID of the database that controls the object. DCM only allows a specific object to be modified in one database in the DCM cluster. In all other databases, that object cannot be modified, except for transitioning it to later states. If the Modifiable In property does not exist, then the controlling database is determined by the From (created_in) property. Typically, files, directories, and projects do not have a Modifiable In property by default.

The figure shows a Rational Synergy Class History View of an object called foo.c. It was created in the Boston database. Therefore, the Local To and From values for the first version (foo.c-1) are both set to the ID of the Boston database (MA). When foo.c is checked out from the Chicago database, the From value is set to the ID of the Chicago database (IL). When foo.c is checked out from the Boston database, the From value is set to the ID of the Boston database (MA). As shown in the figure, the Local To value never changes during the entire history of an object.

In addition to these properties, all DCM objects are assigned attributes that ensure their uniqueness. For example, each object version is linked to a unique cluster ID. These object traits provide security features that:


Feedback