Merging/Branching Brainstorm (db:migrate apply function?) about ruckusing-migrations HOT 4 CLOSED

I should mention, I'm more than willing to help develop it, I am just curious to get others opinions on feasibility, potential pitfalls.

from ruckusing-migrations.

Definitely the system is built towards this goal: to have developers work on different branches of a code base and then later to be able to apply any "missing" migrations for a given machine.

From what I think you're saying, I am not able to reproduce the failure in your scenario:

[cody:ruckusing-migrations (master)]$ php ruckus.php db:generate create_a

    Created migration: 20131213191841_CreateA.php

[cody:ruckusing-migrations (master)]$ php ruckus.php db:generate create_b

    Created migration: 20131213191849_CreateB.php

[cody:ruckusing-migrations (master)]$ php ruckus.php db:generate create_c

    Created migration: 20131213191951_CreateC.php

[cody:ruckusing-migrations (master)]$ mysql -u root ruckusing_migrations -e "INSERT INTO schema_migrations (version) VALUES ('20131213191951')"
[cody:ruckusing-migrations (master)]$ php ruckus.php db:migrate
Started: 2013-12-13 7:21pm UTC

[db:migrate]:
    Migrating UP:
========= CreateA ======== (0.00)
========= CreateB ======== (0.00)


Finished: 2013-12-13 7:21pm UTC

[cody:ruckusing-migrations (master)]$

In this example I create 3 migrations (with a delay between each) and then I manually insert the 3rd migration into the DB as if I have ran it. I then run db:migrate and the system knows it only needs to apply the prior missing ones.

Are you talking about a different scenario?

from ruckusing-migrations.

The scenario you provided does work. One of the issues I was running into though was CreateB failing because something that successfully ran in CreateC (column that no longer exists, etc), thus other important changes in B are never realized in my clone of the project. I interpreted it as CreateB just not running because CreateC already existed, but I now know that is not the case.

I guess that's not so much a function of the code not working as it should, but rather a failure of communication among developers. BTW: I really like this product, and have already added some features, I will be sending in a pull request soon!

from ruckusing-migrations.

You can feel free to close this issue. Thanks.

from ruckusing-migrations.