ErkanaMigrate: Rails-style Migrations Powered by CI 1.6's DBForge

[eluser]Michael Wales[/eluser]
Pre-super-duper Alpha

If you use this in a live project that someone is paying you for I can almost guarantee I will piss myself laughing when it all dies.

This is more a proof of concept and an initial release to get people's opinions on how I attacked the problem of Database versioning.

Most all of the details can be found on my blog: Database Migrations for CodeIgniter 1.6.1, but I'll run through the basics here.

ErkanaMigrate utilizes a table on your database to store current version information (the table name is easily editable and will be automagically created if it doesn't exist). In addition, you will create migration files (once again, location is editable and the directory will be automagically created if possible).

ErkanaMigrate really only features two methods you are worried about: up() and down(). Currently these only go one step in either direction but this will be rectified in future versions. Just call one of these methods from a Controller and watch the magic begin. I highly recommend your protect this controller somehow or you may have a hell of a lot of magic to contend with.

There are also some "entry methods" within the library that make it a bit easier to interface with the DBForge library from your migration files. These don't add a ton of functionality (yet) but due cut down quite a bit on typing.

So, if you are interested in database version control - or simply coding out your database tables in PHP and managing them in a logical manner, please feel free to check out ErkanaMigrate.

I will be actively developing this library and much more involved in its development than ErkanaAuth - so suggestions are highly encouraged.