Constraint Naming Fix
This allows naming of a constraint. Currently, you will only receive the mysql auto named constraint.
Currently only this syntax works: ->addForeignKey( 'client_id', 'clients', 'client_id' )

This fix will allow this syntax to be used: ->addForeignKey( 'client_id', 'clients', 'client_id', array( 'constraint' => 'job_types_ibfk_1', 'delete' => 'RESTRICT', 'update' => 'RESTRICT' ) )
The "constraint" option was not being handled properly, resulting in invalid SQL syntax

Signed-off-by: Jonathan Galpin <jonathan@iqzero.net>
Unique Index Bug Fix

The UNIQUE index option would always set an index type to UNIQUE whether true or false:

Either
'unique' => true
or
'unique' => false

would both result in the index being UNIQUE. This fixes that.

Unique indexes option only had one setting,
This fixes that, allowing you to set a unique index option as FALSE or TRUE.

Signed-off-by: Jonathan Galpin <jonathan@iqzero.net>
added newline to improve debugging

Signed-off-by: Jonathan Galpin <jonathan@iqzero.net>
Merge branch '0.3.x-dev' of https://github.com/jonathan-galpin/phinx into jonathan-galpin-0.3.x-dev
tabs to spaces
Merge branch 'jonathan-galpin-0.3.x-dev' into 0.3.x-dev