This Migration-Generator generates Migrations in correct order, when referential integrity is used. So on remigrating them at example on a dev-system, local-system or others its possible to migrate the schema without constraint violations.
| Laravel/Lumen | PHP-Version | Migration-Generator | Life Support |
|---|---|---|---|
| 5.x | 7.2 up to 7.4 | 1.0.10 | EOL |
| 6.x | 7.2 up to 7.4 | 1.0.10 | EOL |
| 7.x | 7.2 up to 8.0 | 2.0.0 | Yes |
- PHP 7.2 or higher (php 8 is also supported)
- Pdo_mysql extension
- MySQL 5.7 or higher
You can install this package over composer via
composer require n3xt0r/laravel-migration-generator
You`ll not need to add any ServiceProviders to your Configuration on Laravel, this package will register itself on your project.
When you are using Lumen, make sure you have added following line to your app.php:
$app->register(\N3XT0R\MigrationGenerator\Providers\MigrationGeneratorServiceProvider::class);
This Migrator can be executed over the command line by using following command:
php artisan migrate:regenerate
It will dump all your tables to the database/migrations folder in correct order. So when you are using referential integrity it will write all migrations so that they could be re-migrated without changing manually the order of the migration-files.
Are you unhappy with the exported migrations? When you should need some customizations on it, it would be possible to customize the export by extending the export-classes over the DI-Container.
There is a Configuration file called "migration-generator", that you could publish and customize. Every Export-Function like "exporting fields" or "exporting indexes" or else has a Definition- and a Mapping-Class.
Definition-Classes are classes that define the internal runtime export-format. They are used to generate the Schema-Results to a universal format, so that you or anyone else could extend it.
Mapping Classes are classes that converts internal universal format to executable php-code inside the migration-classes.