The migSteps subfolder is located in the implementation folder that contains all of the logic and data regarding a version transition. This folder contains all migration steps required for version transition, which implement the IMigrationStep interface. The IMigrationStep interface provides help functions that package database-specific dependencies and that are not dependent on database-specific requirements. The following methods are not implemented by the abstract superior class BaseMigrationStep and must be implemented in the specific migration step.
Provides the description of the step as a string.
Carries out the step. All public methods of IMapping can be used.
The following methods can be overwritten in the specific migration step.
Determines the order (priority) of the steps to be performed. The default implementation always returns the order number 0. Overwrite this function and enter a number larger than 0, according to the position at which this step should be carried out. The lower the number the higher the priority.
Specifies whether this step should be carried out (return true) or not (return false). The default implementation returns true. The step is thus active and is carried out. Overwrite this function if you want to temporarily turn off a step during development. Some steps, such as the generation of database indices, should be deactivated as soon as a follow-up version is available. Indices should then be generated in the last version transition only.
The interface provides other useful functions for processing data and data structures. These are documented in the Java documentation.