The AbstractMigration class is for end users to extend from when creating migrations. Extend this class and implement the required up() and down() methods.
The AbstractFileConfiguration class is responsible for loading migration configuration information from a file.
The ArrayConfiguration class is responsible for loading migration configuration information from a PHP file.
The Configuration class is responsible for defining migration configuration information.
The ConnectionLoaderInterface defines the interface used to load the Doctrine\DBAL\Connection instance to use for migrations.
The ArrayConnectionConfigurationLoader class is responsible for loading a Doctrine\DBAL\Connection from a PHP file that returns an array of connection information which is used to instantiate a connection with DriverManager::getConnection()
The ConnectionConfigurationChainLoader class is responsible for loading a Doctrine\DBAL\Connection from an array of loaders. The first one to return a Connection is used.
The ConnectionConfigurationLoader class is responsible for loading a Doctrine\DBAL\Connection from the Migrations Doctrine\Migrations\Configuration\Configuration::getConnection() method.
The ConnectionHelperLoader is responsible for loading a Doctrine\DBAL\Connection from a Symfony Console HelperSet.
The YamlConfiguration class is responsible for loading migration configuration information from a JSON file.
The XmlConfiguration class is responsible for loading migration configuration information from a XML file.
The YamlConfiguration class is responsible for loading migration configuration information from a YAML file.
The DepenencyFactory is responsible for wiring up and managing internal class dependencies.
The EventDispatcher class is responsible for dispatching events internally that a user can listen for.
Listens for onMigrationsMigrated and, if the connection has autocommit makes sure to do the final commit to ensure changes stick around.
The MigrationEventsArgs class is passed to events not related to a single migration version.
The MigrationsVersionEventArgs class is passed to events related to a single migration version.
The Events class contains constants for event names that a user can subscribe to.
The FileQueryWriter class is responsible for writing migration SQL queries to a file on disk.
The Finder class is responsible for for finding migrations on disk at a given path.
The GlobFinder class finds migrations in a directory using the PHP glob() function.
The MigrationDeepFinder interface denotes a MigrationFinder that recursively finds migrations in a directory.
The MigrationFinder interface defines the interface used for finding migrations in a given directory and namespace.
The RecursiveRegexFinder class recursively searches the given directory for migrations.
The DiffGenerator class is responsible for comparing two Doctrine\DBAL\Schema\Schema instances and generating a migration class with the SQL statements needed to migrate from one schema to the other.
The FileBuilder class is responsible for building a migration SQL file from an array of queries per version.
The Generator class is responsible for generating a migration class.
The SqlGenerator class is responsible for generating the body of the up() and down() methods for a migration from an array of SQL queries.
The MigrationPlanCalculator is responsible for calculating the plan for migrating from the current version to another version.
The MigrationRepository class is responsible for retrieving migrations, determing what the current migration version, etc.
The Migrator class is responsible for generating and executing the SQL for a migration.
The MigratorConfiguration class is responsible for defining the configuration for a migration.
The OutputWriter class is responsible for writing output to the command line when executing migrations.
The ParameterFormatter class is responsible for formatting SQL query parameters to a string for display output.
The ParameterFormatterInterface defines the interface for formatting SQL query parameters to a string for display output.
The LazySchemaDiffProvider is responsible for lazily generating the from schema when diffing two schemas to produce a migration.
The OrmSchemaProvider class is responsible for creating a Doctrine\DBAL\Schema\Schema instance from the mapping information provided by the Doctrine ORM. This is then used to diff against your current database schema to produce a migration to bring your database in sync with the ORM mapping information.
The SchemaDiffProvider class is responsible for providing a Doctrine\DBAL\Schema\Schema instance that represents the current state of your database. A clone of this Schema instance is passed to each of your migrations so that you can manipulate the Schema object. Your manipulated Schema object is then compared to the original Schema object to produce the SQL statements that need to be executed.
The SchemaDiffProviderInterface defines the interface used to provide the from and to schemas and to produce the SQL queries needed to migrate.
The SchemaProviderInterface defines the interface used to create a Doctrine\DBAL\Schema\Schema instance that represents the current state of your database.
The StubSchemaProvider takes a Doctrine\DBAL\Schema\Schema instance through the constructor and returns it from the createSchema() method.
The QueryWriter defines the interface used for writing migration SQL queries to a file on disk.
The Rollup class is responsible for deleting all previously executed migrations from the versions table and marking the freshly dumped schema migration (that was created with SchemaDumper) as migrated.
The SchemaDumper class is responsible for dumping the current state of your database schema to a migration. This is to be used in conjunction with the Rollup class.
The Stopwatch class wraps the Symfony Stopwatch class so that we do not directly depend on it.
The BooleanStringFormatter class is responsible for formatting a string boolean representation to a PHP boolean value.
The BytesFormatter class is responsible for converting a bytes integer to a more human readable string.
The AbstractCommand class provides base functionality for the other migrations commands to extend from.
The DiffCommand class is responsible for generating a migration by comparing your current database schema to your mapping information.
The DumpSchemaCommand class is responsible for dumping your current database schema to a migration class. This is intended to be used in conjuction with the RollupCommand.
The ExecutCommand class is responsible for executing a single migration version up or down.
The GenerateCommand class is responsible for generating a blank migration class for you to modify to your needs.
The LatestCommand class is responsible for outputting what your latest version is.
The MigrateCommand class is responsible for executing a migration from the current version to another version up or down. It will calculate all the migration versions that need to be executed and execute them.
The RollupCommand class is responsible for deleting all previously executed migrations from the versions table and marking the freshly dumped schema migration (that was created with DumpSchemaCommand) as migrated.
The StatusCommand class is responsible for outputting what the current state is of all your migrations. It shows what your current version is, how many new versions you have to execute, etc. and details about each of your migrations.
The UpToDateCommand class outputs if your database is up to date or if there are new migrations that need to be executed.
The VersionCommand class is responsible for manually adding and deleting migration versions from the tracking table.
The ConnectionLoader class is responsible for loading the Doctrine\DBAL\Connection instance to use for migrations.
The ConsoleRunner class is used to create the Symfony Console application for the Doctrine Migrations console.
The ConfigurationHelper class is responsible for getting the Configuration instance from one of the supported methods for defining the configuration for your migrations.
The ConfigurationHelperInterface defines the interface for getting the Configuration instance to be used for migrations.
The MigrationDirectoryHelper class is responsible for returning the directory that migrations are stored in.
The MigrationStatusInfosHelper class is responsible for building the array of information used when displaying the status of your migrations.
The TableDefinition class is responsible for defining the schema of the table used to track the execution state of each migration version.
The TableManipulator class is responsible for creating and updating the schema of the table used to track the execution state of each migration version.
The TableStatus class is responsible for checking if the tracking table needs to be created or updated.
The TableUpdater class is responsible for updating the tracking table schema if it needs to be updated.
The AliasResolver class is responsible for resolving aliases like first, current, etc. to the actual version number.
The Direction class contains constants for the directions a migration can be executed.
The ExecutionResult class is responsible for storing the result of a migration version after it executes.
The Executor class is responsible for executing a single migration version.
The ExecutorInterface defines the interface used for adding sql for a migration and executing that sql.
The Factory class is responsible for creating instances of the Version class for a version number and a migration class name.
The State class contains constants for the different states a migration can be in during execution.
The Version class represents a single migration version. It wraps around your migration class that extends the AbstractMigration class.