postgres schema
fixed phunit configs
Added information about PDOs
Update migrations.rst
#170 : Try to locate phinx.php

If no config file passed as arg, try phinx.yaml and fallback to
phinx.php. Exception still ask for phinx.yaml as it is intended
behavior.
Allows column types with extra info.

This was breaking my migrations when I have columns with unsigned. I did tests with a online tool, you can find the link here: http://www.phpliveregex.com/p/4E4
Merge pull request #1 from robmorgan/0.3.x-dev

merge back
Rewrite default config files loading

use a loop for possible values, stack exceptions and return the first
one if no match after all.
Updates self:: References to static::

Replaces several `self::` references with late static binding `static::` references, which gives a more predictable reference behaviour.
	modified:   src/Phinx/Db/Adapter/PostgresAdapter.php
The modification allows now migrations to create tables in a schema
"public or other" using the "standard" table api.
============== Config Example ==============
 development:
        adapter: pgsql
        host: localhost
        name: development
        user: development
        pass: you wish!
        schema: zf2test
        port: 5432

============================================
sample migration
use Phinx\Migration\AbstractMigration;

class MyFirstMigration extends AbstractMigration
{
    /**
     * Change Method.
     *
     * More information on this method is available here:
     * http://docs.phinx.org/en/latest/migrations.html#the-change-method
     *
     * Uncomment this method if you would like to use it.
     *
    */
    // public function change()
    // {
    // }

    /**
     * Migrate Up.
     */
    public function up()
    {

        $table = $this->table('userff');
        $table->addColumn('user_id', 'integer')
              ->addColumn('created', 'datetime')
              ->create();
    }

    /**
     * Migrate Down.
     */
    public function down()
    {
        //$this->dropTable('zt2test'.'user_logins');
    }
}

========================================================
migration status result
Status  Migration ID    Migration Name
-----------------------------------------
string(7) "zf2test"
     up  20130925230312  MyFirstMigration

========================================================
migration status result
Status  Migration ID    Migration Name
-----------------------------------------
string(7) "zf2test"
     up  20130925230312  MyFirstMigration
update order of possible config file

As discussed with @garex.
Remove else for @eridal
removing primary_key as a type. fixes #95
Merge branch 'patch-1' of https://github.com/saada/phinx into saada-patch-1
Merge branch 'saada-patch-1' into 0.3.x-dev
Always use a "phinx_" prefix with in tests
Bugfix

* Fixed implementation of SQLite autoincrement that was commented 
* Fixed the regular expression in changeColumn method that caused error to modify the attributes of the column
Merge pull request #273 from vitormattos/patch-1

Bugfix
Merge pull request #213 from andersonamuller/patch-1

Allows column types with extra info.
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>