Phoenix
Framework agnostic database migrations for PHP.
Features
- Validation all settings in migration before executing first query
- Multiple migration directories
- Migrate up and down
- Print executed queries (in debug mode -vvv)
- Dry run - executing up or down migrations without real executing queries. Command just prints queries which will be executed in non-dry mode
- Add an autoincrement primary column to an existing table
- Dump command for creating migration from existing database
- Diff command for creating diff migration from two existing databases
- Test command for testing new migration executing migrate, rollback, migrate
- Status command that shows list of executed migrations and list of migrations to execute
- json output format for all commands
- Namespaces in migration classes
- Own migration templates
- Easy integration to any PHP application
- PHPStorm suggestions (works even better with deep-assoc-completion plugin)
- Change collation for all existing tables and columns
- Turn foreign keys check on / off in migration
- Simple autowiring in migrations
Supported adapters
- MySql
- PostgreSQL
Installation
Composer
This library requires PHP 7.1 or later (7.2, 7.3, 7.4). It works also on PHP 8.0 and should work on PHP 8.1 too. The fastest and recommended way to install Phoenix is to add it to your project using Composer (https://getcomposer.org/).
composer require lulco/phoenix
Usage
Create configuration file
Create file phoenix.php in the root directory of your project. For example:
<?php
return [
'migration_dirs' => [
'first' => __DIR__ . '/../first_dir',
'second' => __DIR__ . '/../second_dir',
],
'environments' => [
'local' => [
'adapter' => 'mysql',
'host' => 'localhost',
'port' => 3306, // optional
'username' => 'user',
'password' => 'pass',
'db_name' => 'my_db',
'charset' => 'utf8',
],
'production' => [
'adapter' => 'mysql',
'host' => 'production_host',
'port' => 3306, // optional
'username' => 'user',
'password' => 'pass',
'db_name' => 'my_production_db',
'charset' => 'utf8',
],
],
'default_environment' => 'local',
'log_table_name' => 'phoenix_log',
];
Read more about configuration here.
REMEMBER: migrations do some structure changes to the database, therefore the database user used for these migrations has to be able to do these changes.
Commands
To run commands, use command runner vendor/bin/phoenix or vendor/lulco/phoenix/bin/phoenix.
Available commands:
init- initialize phoenixcreate- create migrationmigrate- run migrationsrollback- rollback migrationsdump- create migration from existing databasestatus- list of migrations already executed and list of migrations to executetest- test next migration by executing migrate, rollback, migrate for itcleanup- rollback all migrations and delete log table
You can run each command with --help option to get more information about it or read more here
Init command
Command php vendor/bin/phoenix init initializes phoenix and creates database table where executed migrations will be stored in. This command is executed automatically with first run of other commands, so you don't have to run it manually.
Create first migration
Create command php vendor/bin/phoenix create <migration> [<dir>]
php vendor/bin/phoenix create "FirstDir\MyFirstMigration" second
This will create PHP class FirstDir\MyFirstMigration in file named {timestamp}_my_first_migration.php where {timestamp} represents actual timestamp in format YmdHis e.g. 20160919082117. This file will be created in migration directory second which is configured as __DIR__ . '/../second_dir' (see configuration example above).
create command creates a skeleton of migration file, which looks like this:
<?php
namespace FirstDir;
use Phoenix\Migration\AbstractMigration;
class MyFirstMigration extends AbstractMigration
{
protected function up(): void
{
}
protected function down(): void
{
}
}
Now you need to implement both methods: up(), which is used when command migrate is executed and down(), which is used when command rollback is executed. In general: if you create table in up() method, you have to drop this table in down() method and vice versa.
Let say you need to execute this query:
CREATE TABLE `first_table` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`title` varchar(255) NOT NULL,
`url` varchar(255) NOT NULL,
`sorting` int(11) NOT NULL,
`created_at` datetime NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `idx_first_table_url` (`url`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
You need to implement up() method in your migration class as below:
<?php
namespace FirstDir;
use Phoenix\Database\Element\Index;
use Phoenix\Migration\AbstractMigration;
class MyFirstMigration extends AbstractMigration
{
protected function up(): void
{
$this->table('first_table')
->addColumn('title', 'string')
->addColumn('url', 'string')
->addColumn('sorting', 'integer')
->addColumn('created_at', 'datetime')
->addIndex('url', Index::TYPE_UNIQUE)
->create();
}
}
Or you can use raw sql:
<?php
namespace FirstDir;
use Phoenix\Migration\AbstractMigration;
class MyFirstMigration extends AbstractMigration
{
protected function up(): void
{
$this->execute('CREATE TABLE `first_table` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`title` varchar(255) NOT NULL,
`url` varchar(255) NOT NULL,
`sorting` int(11) NOT NULL,
`created_at` datetime NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `idx_first_table_url` (`url`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;'
);
}
}
Implementation of correspondent down() method which drops table first_table looks like below:
protected function down(): void
{
$this->table('first_table')
->drop();
}
Now you can run migrate command to execute your first migration.
Migrate command
Migrate command php vendor/bin/phoenix migrate executes all available migrations. In this case you will see output like this:
php vendor/bin/phoenix migrate
Migration FirstDir\MyFirstMigration executing
Migration FirstDir\MyFirstMigration executed. Took 0.0308s
All done. Took 0.0786s
If you run this command again, there will be no migrations to execute, so the output looks like this:
php vendor/bin/phoenix migrate
Nothing to migrate
All done. Took 0.0451s
If you want to rollback changes (e.g. you found out that you forgot add some column or index), you can run rollback command, update migration and then run migrate command again. Keep in mind that the best practice is to run rollback command before updating migration code.
Rollback command
Rollback command php vendor/bin/phoenix rollback rollbacks last executed migration. In this case you will see output like this:
php vendor/bin/phoenix rollback
Rollback for migration FirstDir\MyFirstMigration executing
Rollback for migration FirstDir\MyFirstMigration executed. Took 0.0108s
All done. Took 0.0594s
If you run this command again, there will be no migrations to rollback, so the output looks like this:
php vendor/bin/phoenix rollback
Nothing to rollback
All done. Took 0.0401s
Dump command
Command php vendor/bin/phoenix dump dumps actual database structure into migration file. If you don't use Phoenix yet and you have some tables in your database, this command helps you to start using Phoenix easier.
Diff command
Command php vendor/bin/phoenix diff creates migration as diff of two existing database structures. This command can be used when upgrading some system to newer version and you know the structure of both old and new version.
Status command
Run php vendor/bin/phoenix status and show list of migrations already executed and list of migrations to execute. Output is like this:
Executed migrations
+--------------------+---------------------------------------------+---------------------+
| Migration datetime | Class name | Executed at |
+--------------------+---------------------------------------------+---------------------+
| 20160919082117 | FirstDir\MyFirstMigration | 2016-09-26 06:49:49 |
+--------------------+---------------------------------------------+---------------------+
Migrations to execute
+--------------------+---------------------------------+
| Migration datetime | Class name |
+--------------------+---------------------------------+
| 20160921183201 | FirstDir\MySecondMigration |
+--------------------+---------------------------------+
All done. Took 0.2016s
Cleanup command
Cleanup command php vendor/bin/phoenix cleanup rollbacks all executed migrations and delete log table. After executing this command, the application is in state as before executing init command.
php bin/phoenix cleanup
Rollback for migration FirstDir\MyFirstMigration executed
Phoenix cleaned
Test command
Test command php vendor/bin/phoenix test executes first next migration, then run rollback and migrate first migration again. This command is shortcut for executing commands:
php bin/phoenix migrate --first
php bin/phoenix rollback
php bin/phoenix migrate --first
Output looks like this:
php bin/phoenix test
Test started...
Migration FirstDir\MyFirstMigration executing...
Migration FirstDir\MyFirstMigration executed. Took 0.0456s
Rollback for migration FirstDir\MyFirstMigration executing...
Rollback for migration FirstDir\MyFirstMigration executed. Took 0.0105s
Migration FirstDir\MyFirstMigration executing...
Migration FirstDir\MyFirstMigration executed. Took 0.0378s
Test finished successfully
All done. Took 0.2840s
Read more about commands here
4.3k Jan 7, 2023
561 Jan 1, 2023
38 Sep 28, 2022
506 Nov 17, 2022
3.3k Dec 30, 2022
1.4k Jan 1, 2023
2 Aug 22, 2022
1.6k Dec 23, 2022
9 Jan 15, 2022
322 Dec 26, 2022
17 Dec 14, 2022
404 Jan 1, 2023
34 Jul 30, 2021
23 Jul 9, 2022
11 Dec 20, 2022
5.7k Jan 4, 2023