Download the PHP package lulco/phoenix without Composer
On this page you can find all versions of the php package lulco/phoenix. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download lulco/phoenix
More information about lulco/phoenix
Files in lulco/phoenix
Informations about the package phoenix
Phoenix
Framework agnostic database migrations for PHP.
Features
- Comprehensive Validation: Validate all settings in your migrations before executing the first query, ensuring error-free operations.
- Multiple Directories: Manage multiple migration directories with ease, enhancing organizational capabilities.
- View Support: Full support for database views, extending the flexibility of your migrations.
- Bidirectional Migrations: Seamlessly migrate both up and down, allowing for smooth transitions and rollbacks.
- Query Debugging: Print executed queries in debug mode (
-vvv
), providing transparency and aiding in troubleshooting. - Dry Run Mode: Execute migrations in a dry run mode to preview changes without making any actual modifications, ensuring safe deployments.
- Auto-Increment Columns: Effortlessly add an autoincrement primary column to an existing table, simplifying schema modifications.
- Database Dump: Use the dump command to create migrations from an existing database, facilitating easy migration setup.
- Database Diffing: Generate diff migrations between two existing databases, making it simple to synchronize changes.
- Migration Testing: Test new migrations with commands that execute, rollback, and re-execute migrations, ensuring reliability before deployment.
- Migration Status: View a detailed status report of executed and pending migrations, keeping track of your migration history.
- JSON Output: Get outputs in JSON format for all commands, enabling easy integration with other tools and workflows.
- Namespace Support: Use namespaces in migration classes for better organization and code management.
- Custom Templates: Create and use your own migration templates, tailoring the process to fit your specific needs.
- Framework Agnostic: Easily integrate with any PHP application, offering a seamless migration experience.
- Enhanced PHPStorm Integration: Enjoy PHPStorm suggestions, with enhanced support when using the deep-assoc-completion plugin.
- Collation Management: Change collation for all existing tables and columns, providing full control over character set settings.
- Foreign Key Control: Toggle foreign key checks on and off within migrations, offering flexibility during complex schema changes.
- Simple Autowiring: Benefit from simple autowiring in migrations, reducing boilerplate code and enhancing productivity.
Supported adapters
- MySQL
- PostgreSQL
Installation
Composer
This library requires PHP 7.4 or later. It works also on PHP 8.0+. The fastest and recommended way to install Phoenix is to add it to your project using Composer (https://getcomposer.org/).
Usage
Create configuration file
Create file phoenix.php
in the root directory of your project. For example:
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 databasediff
- create migration as diff of two existing database structuresstatus
- 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>]
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:
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:
You need to implement up()
method in your migration class as below:
Or you can use raw sql:
Implementation of correspondent down()
method which drops table first_table
looks like below:
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:
If you run this command again, there will be no migrations to execute, so the output looks like this:
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:
If you run this command again, there will be no migrations to rollback, so the output looks like this:
Dump Command
The php vendor/bin/phoenix dump
command generates a migration file from your current database structure, making it easy to start using Phoenix with existing tables. It’s particularly useful for transitioning between MySQL and PostgreSQL.
Key benefits:
- Quickly create migration files from existing databases.
- Simplify Phoenix onboarding.
- Facilitate database engine transitions.
For detailed usage, see the guide on switching databases.
Diff Command
The php vendor/bin/phoenix diff
command generates a migration by comparing two existing database structures. This is ideal for system upgrades where you have both the old and new version schemas.
For detailed usage, see the Diff Command documentation.
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:
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.
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:
Output looks like this:
Read more about commands here
All versions of phoenix with dependencies
ext-json Version *
ext-pdo Version *
symfony/console Version ^5.2.12|^6.0|^7.0
symfony/finder Version ^5.0|^6.0|^7.0