A version ID attached to a 
Meta description of a database.
 This is EXPERIMENTAL functionality and subject to change in future jOOQ versions.
- Author:
- Lukas Eder
- 
Method SummaryModifier and TypeMethodDescription@NotNull VersionApply a migration to produce a new version.@NotNull Versionapply(String id, Collection<? extends Query> migration) Apply a migration to produce a new version.@NotNull VersionApply a migration to produce a new version.@NotNull VersionApply a migration to produce a new version.@NotNull VersionCommit a newMetarepresentation to the version graph.@NotNull VersionCommit a newMetarepresentation to the version graph.@NotNull VersionCommit a newMetarepresentation to the version graph.@NotNull VersionMerge versions.@NotNull Metameta()The version'sMetarepresentation of the database.@NotNull QueriesProduce a migration to a new version.
- 
Method Details- 
metaThe version'sMetarepresentation of the database.
- 
migrateToProduce a migration to a new version.In jOOQ's commercial distributions, this method allows for migrating between versions in any direction, regardless of which version was "first" in a version graph, or if the two versions are on different branches. The resulting queries are potentially destructive in such a case. Such destructive queries ("UNDO" migrations) are prevented by default, and can be turned on using Settings.isMigrationAllowsUndo().In jOOQ's Open Source Edition, this method only allows for migrating "forward". 
- 
commitCommit a newMetarepresentation to the version graph.This calculates a migration path using Meta.migrateTo(Meta).
- 
commitCommit a newMetarepresentation to the version graph.- See Also:
 
- 
commitCommit a newMetarepresentation to the version graph.- See Also:
 
- 
mergeMerge versions.
- 
applyApply a migration to produce a new version.
- 
applyApply a migration to produce a new version.- See Also:
 
- 
applyApply a migration to produce a new version.- See Also:
 
- 
applyApply a migration to produce a new version.- See Also:
 
 
-