All Classes and Interfaces
Class
Description
Various abbreviation-related utilities.
A migration applied to the database (maps to a row in the schema history table).
Prints a tabular data structure as ASCII text.
Base implementation of Callback from which one can inherit.
Abstraction for database-specific functionality.
This is the recommended class to extend for implementing Java-based Migrations.
The main parser all database-specific parsers derive from.
Reader that strips the BOM from every position in a stream.
This is the main callback interface that should be implemented to handle MigrateDB lifecycle events.
Executes the callbacks for a specific event.
Digest-based checksum that replaces the old Integer checksum.
A facility to obtain classes.
Iterator that can be used to close underlying resources.
CockroachDB recommend the use of retries should we see a SQL error code 40001, which represents a lock wait timeout.
CockroachDB-specific table.
Spring-like template for executing transactions.
A function that provides freshly initialized JDBC connections, possibly from a connection pool.
The context relevant to an event.
The context relevant to a migration executor.
The context relevant to a Java-based migration.
The context relevant to a migration resolver.
Defines a strategy for executing a
SqlCallable against a particular database.Extension point for supported database types.
DB2 connection.
DB2-specific function.
DB2 implementation of Schema.
Db2-specific table.
Db2-specific type.
Handles MigrateDB 's baseline command.
Converts the schema history table into the format used by MigrateDB.
Handles MigrateDB's repair command.
Handles MigrateDB 's automatic schema creation.
Handles the validate command.
Executes the callbacks for a specific event.
JavaBean-style configuration for MigrateDB.
The default execution strategy for a
SQLCallable, which performs a single execution.Implements the default MigrateDB behavior, which combines the various migration sources that can be configured.
Represents a sql statement delimiter.
Derby connection.
Derby database.
Derby implementation of Schema.
Derby-specific table.
An error that occurred while executing a statement.
Spring-like template for executing operations in the context of a database connection.
Marker interface for the configuration data structures of extensions.
Utility class for copying files and their contents.
Finds resources in a base directory and its non-hidden subdirectories.
Migration resolver for a fixed set of pre-instantiated Java-based migrations.
Fluent interface for MigrateDB configurations, which delegates to an instance of
DefaultConfiguration.H2-specific table.
HSQLDB connection.
HSQLDB database.
HSQLDB implementation of Schema.
HSQLDB-specific table.
Apache Ignite Thin connection.
Apache Ignite database.
Apache Ignite implementation of Schema.
Ignite Thin-specific table.
Informix connection.
Informix database.
Informix implementation of Schema.
Informix-specific table.
Interface to be implemented by Java-based Migrations.
Adapter for executing migrations implementing JavaMigration.
Migration resolver for Java-based migrations.
Utility class for dealing with jdbc connections.
Collection of utility methods for querying the DB.
Utility class for dealing with jdbc connections.
A location to load migrations from.
Encapsulation of a location list.
(Almost) drop-in replacement for class path scanning stuff.
Logging frontend for MigrateDB components and extensions.
Pre-defined log system names and auto-detection.
This is the centre point of MigrateDB, and for most users, the only class they will ever have to deal with.
Exception thrown when MigrateDB encounters a problem.
Third-party extensions can contribute additional features through implementations of this interface.
The specific exception thrown when MigrateDB encounters a problem in SQL statement.
This specific exception thrown when MigrateDB encounters a problem in SQL script
Thrown when an attempt was made to migrate an outdated database version not supported by MigrateDB .
Exception thrown when MigrateDB encounters a problem with Validate.
The ordering used by
MigrationInfoService.Executes a migration.
Info about a migration.
Dumps migrations in an ascii-art table in the logs and the console.
Parsing support for migrations that use the standard MigrateDB version + description embedding in their name.
Info about all migrations, including applied, current and pending with details and status.
Resolves available migrations.
The state of a migration.
Log implementation that forwards method calls to multiple implementations.
Spring-like template for executing with MySQL named locks.
MySQL-specific table.
Callback that does nothing.
A callback executor that does nothing.
Oracle connection.
Oracle-specific results and side-effects.
Oracle implementation of Schema.
Oracle object types.
Oracle-specific table.
A sql statement from a script that can be executed at once against a database.
Spring-like template for executing with PostgreSQL advisory locks.
PostgreSQL connection.
A PostgreSQL COPY FROM STDIN statement.
PostgreSQL implementation of Schema.
PostgreSQL-specific table.
PostgreSQL-specific type.
Metadata on the string-based configuration properties supported by
DefaultConfiguration.configure(Properties).Redshift connection.
Redshift database.
PostgreSQL implementation of Schema.
Redshift-specific table.
PostgreSQL-specific type.
Migration resolved through a MigrationResolver.
A migration available on the classpath.
A textual resource (such as a .sql file) used by MigrateDB.
Represents a resource name, parsed into its components.
A facility to obtain loadable resources.
Container for all results, warnings, errors and remaining side-effects of a sql statement.
A class that retries a Callable a given number of times until success is obtained.
Mapper from ResultSet row to object.
SAP HANA database.
SAP HANA implementation of Schema.
SAP HANA-specific table.
The schema history used to track all applied migrations.
An easy way to define SQL migration scripts as code.
An interface analogous to Callable but constrained so that implementations can only throw SqlException, not the more
generic Exception.
SQLite connection.
SQLite implementation of Schema.
SQLite-specific table.
Database migration based on a sql file.
Migration resolver for SQL file resources.
SQL script containing a series of statements terminated by a delimiter (eg: ;).
Callback factory, looking for SQL scripts (named like on the callback methods) inside the configured locations.
Executor for SQL scripts.
Spring-like template for executing with SQL Server application locks.
SQL Server connection.
SQL Server object meta-data.
SQL Server object types for which we support automatic clean-up.
SQLServer-specific table.
A sql statement from a script that can be executed at once against a database.
The statement relevant to an event.
Stop watch, inspired by the implementation in the Spring framework.
Sybase ASE Connection.
Sybase ASE schema (database).
Sybase ASE table.
Azure Synapse connection.
Synapse implementation of Schema.
Spring-like template for executing transactions.
Note: "1.0" and "1.0.0" are considered equivalent by
Version.compareTo(Version) and Version.equals(Object)!A warning that occurred while executing a statement.