You can remove versioning from a schema without performing a schema reorganization, if required (for example, if you did not mean to version the schema or if a reorganization fails).
You cannot remove versioning after performing a schema load into the latest version of a schema with only structural changes. This is not permitted because any method that was recompiled has references to the new versions of classes and properties.
To remove versioning from a schema
In the Schema Browser of the current (committed) schema, select the schema whose versioning you want to remove and then select the Unversion command from the Schema menu. (This is displayed as the Version command when the schema is not currently versioned. For details about toggling schema versioning, see "Versioning a Schema", earlier in this chapter.)
If removal of versioning is attempted when a reorganization is in progress (regardless of whether the reorganization progress dialog is displayed), the load fails. For details about reorganizing schemas, see "
The Unversion Schemas dialog, shown in the following image, is then displayed.
To view details of the changes in the schema version, click the Details button. The Display Version Info window, shown in the following image, is then displayed.
The number of changes made to the latest schema version of all schemas in your JADE database is displayed in parentheses in the title bar of the dialog.
To view schema version information:
In the Date From text box in the Selection Criteria group box, specify the starting date from which schema version changes are to be displayed; for example, 03/07/2005 or 03JULY2005. Enter the date in the ddMMMyyyy format. If you do not specify a value in this text box, the search for changed entities starts at the earliest timestamp; that is, the first date on which an entity was changed in the latest schema version.
In the To text box in the Selection Criteria group box, specify the date up to which schema version changes are to be displayed; for example, 31/07/2005 or 31JULY2005. Enter the date in the ddMMMyyyy format. If you do not specify a value in this text box, the search for changed entities ends on the current date.
In the Entity Name text box of the Selection Criteria group box, specify the name of a specific entity if you want to display schema version changes to that entity only; for example, the TestSchema::JadeScript::test1 method. If you do not enter a value in this text box, all entities that match your other selection criteria are displayed.
In the Type drop-down list box in the Selection Criteria group box, specify the meta schema type whose patch version changes you want to display; for example, ExternalMethod, Class, JadeMethod, Interface, or PrimAttribute. If you do not select a type, schema version changes to all meta schema types are displayed.
Click the Reset button to clear all controls in the Selection Criteria group box; that is, specify all changes for the latest version of all schemas.
Click the Refresh button to initiate the schema version display. Alternatively, click the Close button to abandon your selections.
The display is then initiated. Each schema version change that satisfies any specified search criteria is then displayed in the lower portion of the window when the change is made.
To change from the default descending time sort order, click the list header for the element that you want sorted alphabetically or numerically; for example, click the Entity Name list header to list all entities in alphabetical order.
To display and compare method source changes, double-click the appropriate method entity in the display window. For details, see "Comparing the Current and Latest Version of an Entity", in the following section. For details about inspecting a change in the latest schema version, see "Inspecting an Entity in the Latest Schema Version", later in this chapter.
You can resize the Display Version Info window vertically, to enable you to view more information, if required. (You cannot resize this window horizontally, however.)
To remove versioning from the schema, including all changes made to the schema, click the Unversion button.
This action cannot be undone.
The latest version of the schema and all changes in that schema are then removed and only the current version of schema is displayed in the Schema Browser.
If you add a subschema to a schema that is currently versioned (through the JADE development environment or from a schema load), you cannot remove versioning from the versioned schema. An error message box, advising that the unversioning failed because of subschema dependencies, is displayed when you click the Unversion button on the Unversion Schemas dialog.