v0.10.3

Bug Fixes

• Fixed issues in the Postgresql adapter that would drop the wrong foreign keys when only using column names

Changes

• Hiding some debugging output when using the -v flag. The debugging output referring to the list of files visited by phinx during a migration roll out can still be viewed using -vvv

v0.10.2

Changes

• Improved the warnings when declaring both the change and any of up or down methods in a migration.
• The up() and down() methods were removed fro the MigrationInterface

Bug fixes

• Fixed issue "Dropping FK without constraint name causes unwanted dropping of PK in Postgres" (#574)
• Fixed issue in postgres when using boolean in seeds (#1038)

v0.10.1

Changes

• It is now possible to set the file extension for sqlite databases. It will no longer be forced to be .sqlite3
• Added a warning when the migration class declares both the change() method and any of up() and down as well
• Deprecated AbstractMigration::dropTable()
• Deprecated AbstractMigration::insert()

Bug Fixes

• Fixed the dropTable() method in the Migration class, it was broken in the previous release. Additionally deprecated the method as it is an alias for $this->table($table)->dropTable()->save(). Using the table method is preferred as it gives phinx the opportunity to buffer all actions and execute the at the end after validating them.

v0.10.0

This release is a major breaking change when coming from v0.9.x. Most of the user facing methods in the Migration class stay the same, some of the least used ones are gone. The internals of Phinx have been severely changed, to make room for more features and to create more efficient queries.

New Features

• Faster migrations. Phinx can now bundle changes for the same table into a single statement
• Added a Query builder for SELECT, UPDATE, INSERT and DELETE queries
• Improved schema support for Postgres
• Add support for ROW_FORMAT table option
• Added support for LIMIT for each column in an index
• Ability to specify custom column types by the use of a Literal expression
• Added JSON support for the SQLite adapter

Bugfixes

• Probably too many to list them here :)

v0.9.2

0.9.2 (Saturday, 23 December 2017)

• Pull requests
  • #1169 Apply default collation on tables as per documentation
  • #1214 Simplify multiple primary key quoting
  • #1238 Support PHPUnit 6
  • #1244 Add ordered seeds feature
  • #1246 Added saving column's comment for PostgresAdapter when you add column
• Bug fixes
  • #1181 Fix "Fatal: hasOption() on null" error
  • #1198 Fix chainability for the setColumns call

v0.9.1

0.9.1 (Satruday, 9 September 2017)

• Pull requests
  • #1164 Added a function to migration classes to determine migration direction
• Bug fixes
  • #1173 Fixing configuration item default_migration_table
  • #1170 Fixed regression when setting the pdo object directly in the config

v0.9.0

0.9.0 (Sunday, 3rd September 2017)

• Documentation updates
• Pull requests
  • #1122 SQL exceptions will now produce PHP exceptions
  • #1053 Docker Development Kickstarter
  • #945 Rollback --target using migration name
  • #1070 Supporting namespaces in configuration, Migrations and Seeds
  • #1155 Fill up column values from schema
  • #1148 When execute command seed:run, insert all data to a table in a bulk
• Bug fixes
  • #1111 Fixed error when calling truncateTable() method
  • #1117 Quote column names in the addIndex() method for PostgresSQL
  • #1126 Fix invalid changeColumn regex causing deletions
  • #1093 Fix issue with dropColumn command in SQLite
  • #1091 Fix pgsql quoting in comment clause
  • #1094 Fix varchar to datetime error

v0.8.1

0.8.1 (Monday, 5th June 2017)

• Documentation updates
• Pull requests
  • #768 Support for MySQL unsigned primary keys
  • #1104 Removed support for HHVM
  • #1082 Fixed paths displayed in text output
  • #1055 Text wrapper improvements
  • #1056 Update Input/OutputInterface on cached Manager
• Bug fixes
  • #1060 Fixed rollback on only one migration

v0.8.0

0.8.0 (Tuesday, 28th February 2017)

• Documentation updates
• New features
  • #1045 Rollbacks by start time - Thanks to Daniel Gomes.

Upgrading Phinx to 0.8

• Phinx 0.8 allows for phinx rollback and phinx status to operate on migrations in reverse execution order, rather than reverse creation order. To achieve this new ordering, you will need to add a new entry in your phinx.yml file (or equivalent).

  The setting is called version_order and supports 2 values:

  • creation - this is the default value and matches the standard behaviour of executing rollbacks in the reverse order based upon the creation datetime (also known as version).
  • execution - this is the new value and will execute rollbacks in the reverse order in which they were applied.

  This feature will be of most importance when development of migrations takes place in different branches within a codebase and are merged in to master for deployment. It will no longer matter when the migrations were created if it becomes necessary to rollback the migrations.

v0.7.2

0.7.2 (Tuesday, 28th February 2017)

• Bug fixes
  • #1041 Quote new column name in renameColumn in PostgresAdapter
  • #1048 Do not allow the start_time to be updated when setting a breakpoint