Patch version control enables you to set a numeric patch version that records all additions, deletions, and updates made to schema entities (for example, methods, properties, constants, and so on) until a new patch version number is set and the patch version history is optionally removed when the changed entities in the previous patch version are extracted or a new JADE system is installed. See also "Change Control and Patch Versioning Considerations", in Chapter 1.
Patch version control covers all metadata changes; for example, interfaces, the Relational Population Service (RPS), imported WSDL files, and so on.
Patch versioning, which is completely independent of deltas and the associated change control, enables you to:
Set up a patch number for a selected schema.
Enable (or disable) patch version control for the JADE development database; that is, globally.
Extract changed entities from a specified patch for a specific schema.
Recreate a history of changes made within patch versions.
Display a summary of all changes to a specified patch version, and optionally:
Exclusion of duplicate changes.
All changes, or those within a specified period.
A specific developer whose changes are to be displayed.
Specific entity; for example, a method in a class or a global constant.
Metaschema type; for example, methods, properties, or classes.
Additions, updates, or deletions.
You can also compare all source changes within the patch version, and specify the order in which each element is displayed (for example, in alphabetical order of user or by type of change).
Remove patch history changes to meet specified criteria.
Work on different patches in the same environment.
Set up a hook to the development security module that allows conflict resolution (where a patch is being applied to an entity that currently has an open patch number) by an external system.
Set up development security hooks for rename actions and the JADE Painter.
Maintain patch numbers and extract patch number sources.
Reassign patch numbers.
Remove a patch number history.
Enter a patch number when signing on to the JADE development environment.
From the JADE development environment, the Browse menu provides the Patches command, which enables you to maintain a patch number or obtain a patch summary.
For details, see "Maintaining Patch Numbers" or "Displaying a Patch History Summary". For details about setting up patch control information for a new schema, see "
The JADE Installation Preferences dialog provides the Patch menu, which contains the patch version administration commands listed in the following table.
| Command | For details, see… | Description |
|---|---|---|
| Enable / Disable | Enabling or Disabling Patch Versioning | Enables or disables patch versioning for your database |
| Set Patch Number | Setting Up a Patch Number | Sets a new patch version number |
| Extract Patch | Extracting a Patch Version | Extracts all changed entities in the current patch version |
| Recreate History | Recreating a History of Patch Version Changes | Recreates the history of changes in the current patch version |
| Remove Patch History | Removing a Patch History of Changes | Removes the patch history that matched specified criteria |
For details about enabling patch control extensions (for example, to enable users to select the patch number with which they want to work), see the
As a patch version has two keys (the JADE release version and the patch version), when you change JADE release versions the patch version is changed from 6.3.12.patch-number to 6.3.14.patch-number, for example.
If you require patch versioning when you have upgraded to a new JADE release version, you must enable patch versioning manually, as the new patch version is not automatically enabled.
If you want to override existing patch versions in entities when loading a schema (that is, you do not want to retain the patch number or numbers specified in a loaded schema file), see "