If a change is made to a schema entity that results in the schema being versioned, a reorganization is required to bring the changes into effect.
Structural changes to classes with persistent instances result in these instances being updated when the database is reorganized. Structural changes affecting persistent class instances include:
Adding a property
Deleting a property
Changing the type or length of a property
Changing the definition of a dictionary or collection (ascending keys, uppercase, duplicates, and so on)
Changing the membership of a collection
Changing tuning parameters for a collection
Changing the collection type
Adding a constraint or changing a condition
Adding or changing an inverse definition
Changing an RPS mapping (which versions the schema)
Using JCF commands to remap classes and move class instance
A class may not be marked for reorganization when you add a reference that is an exclusive collection or a virtual property.
Changing a property that is a key causes all collections of which that property is a key to be reorganized.
Properties are matched by name within the hierarchy of the current class. If a property is deleted and a new property added with the same name, the reorganization assumes that the original property was modified. If the type of the property is unchanged, the value is not altered by the reorganization (although the reorganization must still be initiated). Changes to properties in a class require a reorganization of all subclasses of that class that have instances.
If a class with a
For details about performing a reorganization, see "