xethron / migrations-generator

Laravel Migrations Generator: Automatically generate your migrations from an existing database schema.

Laravel Migrations Generator

Generate Laravel Migrations from an existing database, including indexes and foreign keys!

Upgrading to Laravel 5.4

Please note that the Laravel 4 Generator edits have been moved to https://github.com/xethron/Laravel-4-Generators.git to update compatibility.

Laravel 5 installation

The recommended way to install this is through composer:

composer require --dev "xethron/migrations-generator"

In Laravel 5.5 the service providers will automatically get registered.

In older versions of the framework edit config/app.php and add this to providers section:

Way\Generators\GeneratorsServiceProvider::class,
Xethron\MigrationsGenerator\MigrationsGeneratorServiceProvider::class,

If you want this lib only for dev, you can add the following code to your app/Providers/AppServiceProvider.php file, within the register() method:

public function register()
{
    if ($this->app->environment() !== 'production') {
        $this->app->register(\Way\Generators\GeneratorsServiceProvider::class);
        $this->app->register(\Xethron\MigrationsGenerator\MigrationsGeneratorServiceProvider::class);
    }
    // ...
}

Notes:

• Thanks to @jamisonvalenta, you can now generate Migrations in Laravel 5!
• feature/laravel-five-stable was forked from way/generators 3.0.3 and was made Laravel 5.0 ready. Jeffrey Way has discontinued support for Laravel 5, so the other artisan generate: commands may not have been made 5.0 compatible. Investigate the artisan make: commands for substitutes, contribute to Laravel to extend generation support, or fix it and submit a PR to jamisonvalenta/feature/laravel-five-stable.

Laravel 4 installation

Run the following composer command:

composer require --dev "xethron/migrations-generator:~1.3.0"

Next, add the following service providers:

'Way\Generators\GeneratorsServiceProvider',
'Xethron\MigrationsGenerator\MigrationsGeneratorServiceProvider',

And you're set. To double check if its working, run php artisan, and look for the command migrate:generate

Usage

To generate migrations from a database, you need to have your database setup in Laravel's Config.

Run php artisan migrate:generate to create migrations for all the tables, or you can specify the tables you wish to generate using php artisan migrate:generate table1,table2,table3,table4,table5. You can also ignore tables with --ignore="table3,table4,table5"

Laravel Migrations Generator will first generate all the tables, columns and indexes, and afterwards setup all the foreign key constraints. So make sure you include all the tables listed in the foreign keys so that they are present when the foreign keys are created.

You can also specify the connection name if you are not using your default connection with --connection="connection_name"

Run php artisan help migrate:generate for a list of options.

Check out Chung Tran's blog post for a quick step by step introduction: Generate Migrations from an existing database in Laravel 4

Changelog

Changelog for Laravel Migrations Generator

20 November 2016: v2.0.0

• Support for Laravel 5

20 November 2016: v1.3.0

• Add options --defaultIndexNames and --defaultFKNames to use Laravel's default generated names
• --no-interaction support
• Migrate table field comments
• Add connection to migrations if its not the default
• Bugfix:
  • --ignore doesn't ignoring the first table in the list
  • Remove backticks from index names #17
  • Drop foreign keys used incorrect key name #34
  • Remove table prefix from migrations
  • Escape table names and args
  • Map JSON columns as text
  • Boolean default results in empty string

25 July: v1.2.2

• Support for Laravel 4.2
• Support for named foreign keys
• Fix error with --ignore option

29 May: v1.2.1

• Fixed problem with char fields showing up as varchar
• Allow decimal, float, and double to be unsigned
• Allow cascading on foreign key update/delete

16 May: v1.2.0

• Now fully supports for enum fields
• Add support for bit fields as Boolean (Laravel Migration Limitation)

10 May: v1.1.1

• Fix crash when migrating tables that use enum
• Added Tests
• Major refactoring of the code

24 March: v1.1.0

• Ability to add entries into the Migrations Table, so that they won't be run as they already exist.
• Convert Blobs to Binary fields
• Minor Code Changes

Thank You

Thanks to Jeffrey Way for his amazing Laravel-4-Generators package. This package depends greatly on his work.

Contributors

Bernhard Breytenbach (@BBreyten)

License

The Laravel Migrations Generator is open-sourced software licensed under the MIT license

migrations-generator's Issues

Laravel 5.1

Is the installation procedure for the generator the same as Laravel 5? Or do the tools need to be updated to this version. I get a "Class 'Way\Generators\GeneratorServiceProvider' not found" exception when trying to run artisan.

create seed file from the existing data in tables

hi
i think it is good to also create seed file from the existing data in tables

Class 'Xethron\MigrationsGenerator\MigrationsGeneratorServiceProvider' not found

Hi,
I want to use the migrations-generator. Trying the "php artisan" command I get the above error.

Here are my directories, the serviceproviders and the error:
https://gyazo.com/df1642a3b2dbc8c51337de4d71917d89

I'm using Laravel 5, PHP 5.6

Could you please help?

Prefix is not properly detected

DB prefix is set in the settings, but exported migrations keep the prefix text on the table names, causing the table name to be incorrect when you later import it (creates prefix_prefix_tablename)

Couldn't able to fetch comments for a column

I am using L5.1 and it worked fine for me and I am thankful about that.

But ubable to fetch comments from tables so I added them manually.

DB config 'fetch' => PDO::FETCH_ASSOC on enum error

config/database.php 'fetch' => PDO::FETCH_ASSOC on enum error on FieldGenerator.php line 76.

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for xethron/migrations-generator dev-master -> satisfiable by xethron/migrations-generator[dev-master].
- xethron/migrations-generator dev-master requires way/generators 2.* -> no matching package found.

Potential causes:

• A typo in the package name
• The package is not available in a stable-enough version according to your minimum-stability setting
  see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion for more details.

Read http://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

In my composer file:
"require-dev": {
"way/generators": "~3.0",
"xethron/migrations-generator": "dev-master"
}

Export creates a migration for the "migrations" table, causing conflict

The export should always skip the migrations table, since the migrate command will create one, then when it gets to the create_migrations_table migration, it errors. (I've never written the word migration that many times before)

Package not found [solved]

The requested package way/generators dev-feature/laravel-five-stable exists as way/generators[1.0, 1.1, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.6.1, 3, 3.0.1, 3.0.2, 3.0.3, dev-master, dev-rewrite] but these are rejected by your constraint.

Pulling in way/generators:dev-master does work but then the migrations-generator fails with

" - Installation request for xethron/migrations-generator dev-l5 -> satisfiable by xethron/migrations-generator[dev-l5].
- xethron/migrations-generator dev-l5 requires way/generators dev-feature/laravel-five-stable -> no matching package found"

Undefined index: index_type

I got "Undefined index: index_type" error. I followed these steps. I dont know why I got this error.

root@user-System-Product-Name:/var/www/x# php artisan migrate:generate
Using connection: mysql

Generating migrations for: x, y, z, Etc

Do you want to log these migrations in the migrations table? [Y/n] :

Y

Next Batch Number is: 1. We recommend using Batch Number 0 so that it becomes the "first" migration [Default: 0] :

0
Setting up Tables and Index Migrations

[ErrorException]
Undefined index: index_type

TINYINT converted to boolean

using ref 5631ddd

`credit_status` tinyint(4) NOT NULL

becomes

$table->boolean('credit_status');

Migrations attempt to create indices twice.

I have the following line in a generated migration:

$table->float('more_than', 10, 0)->default(25)->index('`more_than`');

Which is in turn generating the following error:

[Illuminate\Database\QueryException]
SQLSTATE[HY000]: General error: 1 index more_than already exists (SQL: create index `more_than` on "discounts" ("more_than"))

Moving the index step to its own line (and removing the backticks, ha ha) works fine:

$table->index('more_than');

But the following line works just fine (backticks and all):

$table->enum('shipmethod', array('1', '2', '3', '4', '5', '6', '7'))->default('1')->index('`shipmethod`');

Unsigned increments('id) takes as increments('id)

Hi,
very useful package! :)

I found this issue: when generating migrations of tables with an unsigned increments('column'), the unsigned part is not taken.
To be some specific, if we take a table created with:

Schema::create('tb_users_assigned_roles', function($table)
    {
        $table->increments('id')->unsigned();
        $table->integer('user_id')->unsigned();
        $table->integer('role_id')->unsigned();
        $table->foreign('user_id')->references('id')->on('tb_users');
        $table->foreign('role_id')->references('id')->on('roles');
    });

migrations-generator creates the following migration:

Schema::create('tb_users_assigned_roles', function(Blueprint $table)
    {
        $table->increments('id');
        $table->integer('user_id')->unsigned()->index('`assigned_roles_user_id_foreign`');
        $table->integer('role_id')->unsigned()->index('`assigned_roles_role_id_foreign`');
    });

that is, the ->unsigned(); part of the first column is lost.

If I find other problems, I'll report them!

enum support?

I'm running into this error:

[Doctrine\DBAL\DBALException]                                                
  Unknown database type enum requested, Doctrine\DBAL\Platforms\MySqlPlatform  
   may not support it.              

My tables have enum() types.

Failed to clone [email protected]:jamisonvalenta/Laravel-4-generators.git, git was not found

I'm getting this error. I should have no typos. Everything is copied directly from the readme.

[RuntimeException]
Failed to clone [email protected]:jamisonvalenta/Laravel-4-generators.git, git was not found, check that it is installed and in your PATH env.
'git' is not recognized as an internal or external command,
operable program or batch file.

"require-dev": {
"fzaninotto/faker": "~1.4",
"mockery/mockery": "0.9.",
"phpunit/phpunit": "~4.0",
"symfony/css-selector": "2.8.|3.0.",
"symfony/dom-crawler": "2.8.|3.0.*",
"xethron/migrations-generator": "dev-l5",
"way/generators": "dev-feature/laravel-five-stable" },

"repositories": {
"repo-name": {
"type": "git",
"url": "[email protected]:jamisonvalenta/Laravel-4-generators.git"
}

Issue with octobercms

I added some custom tables to my octobercms database and would like to generate a model from these tables, using this generator + https://packagist.org/packages/user11001/eloquent-model-generator

Now if I fire "php artisan migrate:generate" or even "php artisan help", the following error will appear:

[ErrorException]
Argument 5 passed to Xethron\MigrationsGenerator\MigrateGenerateCommand::__construct() must be an instance of Illuminate\Config\Repository, i
nstance of October\Rain\Config\Repository given, called in vendor/xethron/migrations-generator/src/Xethron/MigrationsGe
nerator/MigrationsGeneratorServiceProvider.php on line 30 and defined

Any idea how to fix this? Is it possible to use this within a OctoberCMS installation or have a setup another laravel environment for this migration first, and then put it manually it octobercms?

thx for help.

Can it generate migrations for updates since the last generation?

Lets say I'm constructing db structure from EER diagram. Creating, updating, etc. Suppose I generated initial set of migrations. What happens if I change db structure as usually from EER diagram. Will it be able to detect the fact and create migration for changes only?

Now add a travis badge :P

Tests trying to create a table twice

We have the following migration and when we run tests they fail because

PDOException: SQLSTATE[HY000]: General error: 1 there is already a table named block

Here's the migration:

        public function up()
        {
            Schema::create('block', function(Blueprint $table)
            {
                $table->increments('block_id');
                    $table->string('field')->default('')->index('field');
                $table->string('operator', 6)->default('')->index('operator');
                $table->string('block')->default('')->index('block');
                $table->integer('weight')->unsigned()->nullable()->default(1)->index('weight');
                $table->string('added_by', 16)->nullable();
                $table->timestamp('ts')->default(DB::raw('CURRENT_TIMESTAMP'));
            });
        }

I removed the index->() calls and the error went away.

Let me know what other info i can provide that might be of help.

Add scrutinizer-ci support.

laravel 5 not install

composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for xethron/migrations-generator dev-l5 -> satisfiable by xethron/migrations-generator[dev-l5].
- xethron/migrations-generator dev-l5 requires way/generators dev-feature/laravel-five-stable -> no matching package found.

Potential causes:

• A typo in the package name
• The package is not available in a stable-enough version according to your minimum-stability setting
  see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion for more details.

Read http://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Support Laravel 5

Can you bump the version up to support Laravel 5 too.

Stored Procedure Migration

Hi guys,

Sorry if I ask a stupid question, but is it possible in this migration generator that the stored procedure get migrated out as well?

Error on add_foreign_key_to_

When the app create the file add_foreign_key_to_TABLE creates as an example:

up() Method: $table->foreign('account', 'account_fi1kk')->references('number')->on('accounts');
down() Method: $table->dropForeign('account');

Down method isn't correct in laravel 4, must be $table->dropForeign('account_fi1kk'); if not is not possible to rollback because laravel returns an General error: 1025 Error on rename of table because can't remove foreign key

ForeignKeys migrations: drop issue

When generating the dropForeign, laravel asks for the index name. The package is using the field name.

Having this up():

Schema::table('A', function(Blueprint $table)
{
$table->foreign('B_id', 'A_B_id_fkey')->references('id')->on('B')->onUpdate('RESTRICT')->onDelete('RESTRICT');
});

Generates this down:

Schema::table('A', function(Blueprint $table)
{
$table->dropForeign('B_id');
});

Should generate:

Schema::table('A', function(Blueprint $table)
{
$table->dropForeign('A_B_id_fkey');
});

Postgres UUID columns are generated as $table->guid

Postgres UUID columns are generated as $table->guid, resulting in

PHP Fatal error: Call to undefined method Illuminate\Database\Schema\Blueprint::guid()

The right method name is Blueprint::uuid(), so it's temporarily fixed by a replace.
Used versions: Laravel 5.2.10, PostgreSQL 9.3

Hey, since way/generator has supported L5, do i still need to installed the forked one since I have already installed the original way/generator for laravel 5?

Hey, since way/generator has supported L5, do i still need to installed the forked one since I have already installed the original way/generator for laravel 5?

Make all tables innodb?

Hey, could you make an option so we could make it generate all inno db tables? You really just need to make it add the line $table->engine = "InnoDB"; to each create file, and I looked through it but I just couldn't find where I would make changes to make this possible.

In PostgreSQL certain tables contain double quotes when listTableNames() is called

Hi,

when $this->schema->listTableNames(); is called some table names are enclosed by double quotes.
For example table names like "order" or "user"
I know this could be more an issue of doctrine than yours, however i modified the getTables function...

public function getTables()
    {
        $tables = $this->schema->listTableNames();
        if (is_array($tables))
        {
            for ($i = 0; $i < count($tables); $i++)
            {
                if (preg_match('/"/', $tables[$i]))
                {
                    $tables[$i] = str_replace('"', '', $tables[$i]);
                }
            }
        }
        return $tables;
    }

php artisan migrate:generate json type was unsupported.

php artisan migrate:generate

[Doctrine\DBAL\DBALException]
Unknown database type json requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

Didn`t support type json ,my database is mysql version >=5.7 .

artisan error message: classes not found

I followed the instructions on the readme homepage: put the file in composer.json, ran composer update, and got the Way and Xethron PHP libraries put in my vendor dir, and added the two lines of services providers to the providers array in config/app.php. When I try and run "php artisan migrate:generate," I get the following error message:

C:\xampp\htdocs\workflow>php artisan migrate:generate
{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","me
ssage":"Class 'Way\Generators\GeneratorsServiceProvider' not found","file":"C:
\xampp\htdocs\workflow\vendor\laravel\framework\src\Illuminate\Foundati
on\ProviderRepository.php","line":123}}{"error":{"type":"Symfony\Component\De
bug\Exception\FatalErrorException","message":"Class 'Way\Generators\Generato
rsServiceProvider' not found","file":"C:\xampp\htdocs\workflow\vendor\larav
el\framework\src\Illuminate\Foundation\ProviderRepository.php","line":123}}

How do I fix this?

Boolean with default value: false -> ' '

I have some booleans, not nullable, with default value: false.
The generated migration change the default to "blank": ->default('');

Greets

Double converted to float(10,0)

Hi,
I've just tested your generator and its working pretty well. I just noticed that double columns are converted to float(10,0). Is this behaviour intended?

Greets

Unsupported operand types error with --ignore option

Any ideas? Works without --ignore option.

{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"Unsupported operand types","file":"...../vendor/xethron/migrations-generator/src/Xethron/MigrationsGenerator/MigrateGenerateCommand.php","line":145}}

Is this work for SQL SERVER

I have application using C# and SQL server , now i want to generate model from SQL Server exists database and re-create on MySQL, is this work for SQL Server?
Thanks

unique colums are not unique after generation

The generate operation doesn't keep the columns unique, the unique option seems to be completely ignored. I have only indexed unique columns in the table I've experienced the issue with - the indexes are exported correctly, but the unique option is gone after generation.

before:

$table->string('xx');
$table->index('xx');
$table->unique('xx');`

after:

$table->string('xx')->index();

JSON datatype not handled for PostgreSQL

I'm using PostgreSQL and I have two tables with a JSON datatype. When generating migrations it throws the error "Unknown database type json requested, Doctrine\DBAL\Platforms\PostgresqlPlatform may not support it".

I fixed it by adding:

$connection->getDatabasePlatform()->registerDoctrineTypeMapping('json', 'string');

to \Xethron\MigrationsGenerator\Generators\SchemaGenerator in the constructor

Problem on composer update

Problem

When running composer update.

Problem 1
    - Installation request for xethron/migrations-generator dev-master -> satisfiable by xethron/migrations-generator[dev-master].
    - xethron/migrations-generator dev-master requires way/generators 2.* -> no matching package found.

Fixed

I had "way/generators": "dev-master" installed.

Thanks for the script.

Foreign Keys and Cascades

Hi,
migrations for foreign keys are properly generated but those cascades like "onDelete" won't be added to the migrations.

Export should account for the prefix

The export process grabs the tables exactly as they are in the db. So, if you have a prefix set, when you run the migration again you'll have prefix__prefix__tablename which breaks all kinds of stuff.

Since the prefix is set on the database configuration, it should be removed from the table names when exporting.

Column name with reserved character generates incorrect migration

Supposing you have this:

mysql> create table test (`foo.bar` int);
Query OK, 0 rows affected (0.05 sec)

mysql> describe test;
+---------+---------+------+-----+---------+-------+
| Field   | Type    | Null | Key | Default | Extra |
+---------+---------+------+-----+---------+-------+
| foo.bar | int(11) | YES  |     | NULL    |       |
+---------+---------+------+-----+---------+-------+
1 row in set (0.00 sec)

Then the generated migration $table->integer('foo.bar')->nullable(); is incorrect: Eloquent explodes that to a table name and column, that is this incorrect SQL:

create table test (`foo`.`bar` int);  /* oops, no table `foo` */

The proper generation should be:

$table->integer(DB::raw('`foo.bar`')->nullable();

where both the list of reserved characters and the escape character is driver-specific. The patch for this seems straightforward: if the column name contains a driver-specific reserved character, wrap the generation in a DB::raw using the driver-specific escape character. Possibly an even simpler solution is to wrap ALL column names in DB::raw...

P.S.: I'm not saying a column like this is a good idea! I did just encounter it, though, reversing a legacy system.

Way/Generators -> Laracasts/Generators

I'm not sure Way's new generator is simply not working with yours, or just that you didn't informed?

https://github.com/laracasts/Laravel-5-Generators-Extended

Lumen

Hi there,

Is it possible to have migrations-generator in Lumen too?

trying to use it in Lumen but failed.

Here my composer.json looks like

Xethron/migrations-generator could not be found

"require-dev": {
"fzaninotto/faker": "~1.4",
"mockery/mockery": "0.9.",
"phpunit/phpunit": "~4.0",
"symfony/css-selector": "2.8.|3.0.",
"symfony/dom-crawler": "2.8.|3.0.*",
"xethron/migrations-generator": "dev-15",
"way/generators": "dev-feature/laravel-five-stable"
},

"repositories": {
"repo-name": {
"type": "git",
"url": "[email protected]:jamisonvalenta/Laravel-4-generators.git"
}
}

in my composer.json, I receive the error

"Xethron/migrations-generator could not be found or there is a typo"

I have followed the instructions to the letter on the library home page.

The requested package way/generators could not be found in any version

Error when using composer update on laravel v5.1.17:

Problem 1
- The requested package way/generator could not be found in any version, there may be a typo in the package name.
Problem 2
- Installation request for xethron/migrations-generator dev-l5 -> satisfiable by xethron/migrations-generator[dev-l5].
- xethron/migrations-generator dev-l5 requires way/generators dev-feature/laravel-five-stable -> no matching package found.

Support for calling migrate:generate in application.

I am looking to use this package in the application as such: Artisan::call('migrate:generate');. The interactive questions however limit me from doing so.

I'd like to propose integrating support for the --no-interaction option and falling back to the default values for this.

boolean field is not migrated properly

I have a table with boolean field with default value set as false. When I run migration it shows
$table->boolean('deleted')->default('');
default is shown as null field. Can you please check and let me know a solution for same

Does not make "generate" functions compatible with L5

Although this adds the "generate" functions to artisan, they do not work with Laravel 5, only migrate:generate has been made to work with L5. Perhaps a note stating this in the readme would be useful.

Updated: It seems as though some of the generate functions do work as expected, resource for example. scaffold does not however.

Backticks around index names are MySQL specific

The generated migrations have backticks in the index names, like this:

$table->integer('affiliate_id')->index('`affiliate_actions_affiliate_id`');

These cause errors in PostgreSQL, as the backtick character is not ANSI SQL, and is specific to MySQL only.

Error text in console from Artisan:

  [Illuminate\Database\QueryException]
  SQLSTATE[42601]: Syntax error: 7 ERROR:  syntax error at or near "`"
  LINE 1: create index `admins_user_id` on "admins" ("user_id")
                       ^ (SQL: create index `admins_user_id` on "admins" ("user_id"))

Index names without the backticks works fine, however:

$table->integer('affiliate_id')->index('affiliate_actions_affiliate_id');

error on install of dev-master on windows 7

Ran composer update with "xethron/migrations-generator": "dev-master"
in composer.json and got this error:

{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"Class 'IlluXethron\MigrationsGenerator\MigrationsGeneratorServiceProviderminate\Workbench\WorkbenchServiceProvider' not found","file":"C:\Users\norm\trivia\bootstrap\compiled.php","line":4219}}Script php artisan clear-compiled handling the post-update-cmd event returned with an error

Problem may be that the namespace statement is on the same line as the php header in MigrationsGeneratorServiceProvider.php. It may not have been caught on linux but Windows may be sensitive to this: