Create an Initial Migration from an Existing Database

[ylynfatt]

Is it possible for Phinx to create an initial migration from an existing database? My scenario is that I have an application with a database and it's tables already and I'd like to start using Phinx to handle my migrations (previously i was manually creating SQL scripts). I'd love if Phinx could inspect my database and create an initial migration file with the current table structures as a starting point.

I hope that made sense.

[kmentch]

I would love to see this feature as well.

[robmorgan]

I'll leave this issue open - happy to review a PR, but I won't be working on it personally for now.

[detook]

I've started to work on this today. I see following implementation:

1. phinx schema:dump creates phinx migration at migration_folder/schema/schema.env.php
2. schema.env.php can be migrated using phinx schema:load. In this case old schema will be desrtoyed.
3. phinx schema:dump runs every time after migrate and rollback.

Any comments?

PS. I don't know for now how to deal with missing data type. For example, target table has tinyint field. $table->getColumns() will throw an exception in this case. I think fetching columns and type check shoud be separated. @robmorgan please comment.

Thanks

[detook]

Regarding missing data types - I looked to wrong method. Sorry. Everything is fine here

[ylynfatt]

@detook This sounds good to me for an initial implementation. Can't wait to try it out.

[iwootten]

@detook I've been attempting to use your fork, but can't see the "schema-dump" command available in the list of commands in the CLI on the schema-dump branch. Am I missing something obvious?

I was about to tackle this request myself, but given you're already making headway, I'd like to see if I can use it.

[detook]

Does PhinxApplication's constructor has $this->add(new Command\SchemaDump()); line?

@iwootten, you could help with schema-load command. My fork does basic dump right now, primary and foreign keys will be added during the weekend.

[iwootten]

@detook Yes it's there. I've faked a composer directory vendor/detook/phinx and switched to your branch under there. php vendor/detook/phinx/bin/phinx doesn't seem to give me anything extra.

Happy to help if I can.

[detook]

@iwootten try following:

1. Tell composer to use my branch.

"repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/detook/phinx.git"
        }
],
"require": {
        .....
        "robmorgan/phinx": "dev-schema-dump",
        .....
}

2. Or clone repository as standalone project and develop with TDD. After successful tests try code on real database.

[iwootten]

@detook great, that gets me to use of the command, but it yields a runtime exception when I try to execute it.

"[RuntimeException] The type: "" is not supported."

schema-dump [-c|--configuration="..."] [-p|--parser="..."] [-e|--environment="..."]

[detook]

Great! Looks like Phinx failed to guess your field type. Usually it happens when field has attributes like int(4) unsigned. This is one my TODOs. Let me know.

By the way, I'm working only with MySQL first so other adapters do not work.

[iwootten]

@detook, looks like you're right. I'm using MySQL, so that's no problem. A simpler table gets written out by the dump tool to a migrations directory as expected.

[detook]

@iwootten, latest commit f0f9ebc should dump fields with attributes

[Rican7]

I never do this, but I would LOVE to see this feature. To be honest, without it migrations are only half-useful.
I give this a 👍