jmhobbs / kohana-3-migrations

A simple, SQL based migrations system for Kohana 3.

About

This Kohana module provides simple migrations from the command line for SQL compliant databases.

It is a K3 port of http://github.com/jmhobbs/kohana-2-migrations

Using

Create a folder named "migrations" in your application folder. This directory must be writable, or must contain a directory called ".info" which is writable.

Put valid SQL files in that folder, following the naming patterns: 001_ANYTHING_HERE_UP.sql & 001_ANYTHING_HERE_DOWN.sql

For example:

001_Auth_DOWN.sql
001_Auth_UP.sql
002_Users_DOWN.sql
002_Users_UP.sql
003_Island_DOWN.sql
003_Island_UP.sql
004_Pages_DOWN.sql
004_Pages_UP.sql

Now add this module to your application/bootstrap.php file.

Then you can run them from the command line:

Status

jmhobbs@katya:/var/www/qaargh$ php5 index.php --uri=migrations

=======================[ Kohana Migrations ]=======================

    Current Migration: 7
     Latest Migration: 7

===================================================================

Up

jmhobbs@katya:/var/www/qaargh$ php5 index.php --uri=migrations/up/3

=======================[ Kohana Migrations ]=======================

   Current Migration: 0
    Latest Migration: 7

===================================================================

  Requested Migration: 3
            Migrating: UP

===================================================================

Migrated: 001_Auth_UP.sql
Migrated: 002_Users_UP.sql
Migrated: 003_Island_UP.sql

===================================================================

    Current Migration: 3
     Latest Migration: 7

===================================================================

Down

jmhobbs@katya:/var/www/qaargh$ php5 index.php --uri=migrations/down/0

=======================[ Kohana Migrations ]=======================

    Current Migration: 3
     Latest Migration: 7

===================================================================

  Requested Migration: 0
            Migrating: DOWN

===================================================================

Migrated: 003_Island_DOWN.sql
Migrated: 002_Users_DOWN.sql
Migrated: 001_Auth_DOWN.sql

===================================================================

    Current Migration: 0
     Latest Migration: 7

===================================================================

Authors

• John Hobbs (jmhobbs)
• Kevin Warrington (dubbs)

License

Copyright (c) 2010-2012

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Inspiration

Inspiration and base code from https://code.google.com/p/kohana-migrations/

kohana-3-migrations's Issues

.sql files are weak

Hey,

Although this is awesome code, basing your migrations around .sql files is a bit weak. In Rails, CodeIgniter and Fuel migrations are done with .rb or .php files, which means you can run SQL and any other code too.

For example, if I add a new column to a table and my model or controller is expecting that value, I'll need to clear the cache to stop a PHP errors popping up. This is only one of several possible examples.

Run a PHP file and you can do lots more. :)

Can't create stored procedures in migration script.

Migrations simply splits the script at semicolons to get queries. This fails with stored procedures, which exactly for that reason use the DELIMITER command to temporarily redefine the delimiter.

Here's a Stackoverflow answer where somone solved that problem, maybe you could ask them if you can use the code: http://stackoverflow.com/a/5025730/16883

3.2 Compatibility

Bring everything up to speed with 3.2.