- Fix LogPendingMojo name in annotation
- Allow for configuring dialect in Mojos
- Add BaselineMojo
- Add a way to explicitly create a baseline via API
- Remove TODO doclink for now. We'll update all the exceptions later
- Rename Settings.migrationAllowsUndo to migrationAllowUndo
- Snapshots are a commercial only feature
- Add Settings.migrationAllowInvalidCommits
- Improve invalid commit exception message
- GitCommitProvider message uncommitted-and-untracked
A SCRIPT is allowed to modify a schema that is otherwise managed by SCHEMA files. There must be a SCHEMA file documenting the outcome. Other than for that purpose, that SCHEMA file must be ignored, and no diff must be applied from the previously known SCHEMA file.
This currently only works if the SCHEMA and SCRIPT files are contained in the same Commit. It's currently not possible to fix a mistake, where the SCHEMA file has been forgotten, other than to edit the SCRIPT file.
- Snapshots will be a commercial only feature
- CommitImpl should reject duplicate paths
- Add the ContentType.SCRIPT implementation
- Files.writeString() wasn't available in JDK 8 yet
- Improved DefaultMigrationContext::toString
- Updated TODO list
- Added migration client info to HISTORY table
- Handle missing decrements
- Throw exception when attempting to decrement a deletion (for now)
- Ignore snapshots when backwards migrating
- Move LogMojo and HistoryMojo logic into org.jooq.Migration
- Reduce log level in FilePattern to DEBUG
- Rename SnapshotMojo to AddSnapshotMojo
- Rename AddMojo to AddUntrackedMojo
- AddUntrackedMojo should append to the file, not overwrite it
- Add fileName property to AddSnapshotMojo and AddUntrackedMojo
- Rename HistoryMojo to LogHistoryMojo
- Add a LogMigrationMojo
- Add a LogUntrackedMojo
- Add History::available
- Allow for updating the root node after all, in order to allow for creating baselines on existing databases
- [jOOQ/jOOQ#17646] Ignore unnamed constraint changes in both directions
- Expose Migration::untracked, publicly
- Add an AddMojo to add untracked files to the migration
Users may use unnamed constraints in migration scripts. When comparing the schema with the existing schema in the database, we must ignore the database's synthetic constraint names.
- Handling of default schema in MigrationImpl::revertUntrackedQueries
- Use Settings.migrationHistorySchema in revertUntrackedQueries
- Improve logic to filter out history table from revertUntrackedQueries
- Set migration default schema as interpreter search path in History
- Suppress exceptions caused by history record re-insertion in case of
DataMigrationRedoLogException
- VersionImpl should apply CREATE SCHEMA IF NOT EXISTS to on init
- Remove weird initialisation of VersionImpl.meta with interpreter
search path
- Implement DefaultMigrationContext::toString
- Automatically set interpreter search path in Maven plugin
- GitCommitProvider should use same content type subdirs (in plural)
- Add commitProvider property to Maven plugin
- Upgrade jgit
- Allow for configuring a basedir within the GitConfiguration#repository
- Don't throw exceptions in HistoryImpl::toString
- LogMojo should log history as well
- Reuse FilePattern::fileComparator also to sort IDs when loading files
- LogMojo should also include HistoryMojo output
- Make CommitType::getId optional for per-SQL-file metadata usage
