Overview

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:

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 JadeBytes attribute is modified in a way that does not affect the Unstructured Data Resource (UDR) file or files (for example, by adding an Integer property), the resulting reorganization skips the UDR file or files.

For details about performing a reorganization, see "Performing a Reorganization", in Chapter 3 of the JADE Development Environment User’s Guide. For details about RPS changes that cause a reorganization, see "Schema Instantiation", in Chapter 2 of the JADE Synchronized Database Service (SDS) Administration Guide.