Extract
The extract command provides the ability to perform a deep extract of all or specified schemas (to the repository currently open).
This command is used during migration to populate a new source repository, but may also be used to re-extract schemas for an existing repository (possibly needed in scenarios where changes cannot be made via the IDE with JadeGit enabled).
The --schemas option may be used to specify one or more schemas to extract (and these may be a regular expression). By default, all schemas will be extracted, excluding schemas supplied by Jade or JadeGit (CardSchema, JadeReportWriterSchema & JadeGitSchema).
The --commit-message option may be used to specify the message for a commit to be created following the extract, if any changes are extracted. The --commit-force option forces the creation of a new commit, irrespective of any changes being extracted.
The --original-commit option may be used to specify a commit created previously when an extract is being repeated.
When an ID needs to be allocated for a new entity being extracted (in comparison to the commit referred to by current branch), the original commit contents are queried to determine if the entity has been extracted previously, in which case the ID allocated previously is reused.
When a commit message is specified, and a new commit isn't being forced, the original commit may be preserved, if the original contents, message & parent all match what would be used to create a new commit.
Overall, this option provides the ability to repeat an extract cycle (i.e. for migration purposes), in order to apply any changes retrospectively (i.e. source changes or new version of JadeGit), while preserving existing commits wherever possible in order to minimize disruption caused otherwise by rewriting the history entirely.
Last updated
