Patches

A patch is a comparison between a release and a target repository in the database. Once a repository version has been released, you can create patches for this release.

When creating a patch, first an export is made of the target repository. Usually, this is the repository version of the release. Then, the patch (comparison) is created.

NAMING CONVENTIONS:

The file name for a patch is based on the repository code and release nr. of the release, the patch number, and the current Folder Location settings:

<Releases folder>\<Repository Version Code>_<release nr>_patch<patch_nr>.xml

For example:

C:\XML Repository Manager\releases\TRAVEL8_802A_patch2.xml

A generated XML patch can be transformed to a USoft Import XML document. This document can be used to apply the patch to a repository that is identical to the release. Actually, this is why it is called a patch.

The generated XML patch can also be transformed to a PDF report. This PDF difference report shows green inserted records, red deleted records, and blue updated records.

Currently, a patch can be applied in two ways. This may be enhanced in the future:

·	In the SQL Command Dialog box of the Definer of the SOURCE repository, you can issue statement:

SELECT TO_CLOB(xml.import(<MyComparison.imp.xml>))

·	You can define a task set with an import task, that enables you to import differences into a repository in a batch-like manner.

For more details, refer to: Task Sets.