Revision history for SHARYANTO-SQL-Schema

0.10    2014-09-06 (PERLANCAR)

        - Allow creating from an earlier version using 'install_v<VERSION>' in
          the spec and set option 'create_from_version' => <VERSION> when
          calling the function. This is useful for testing database migration.


0.09    2013-09-06 (SHARYANTO)

        - Document that 'latest_v' is required in spec. On the other hand, ...

        - Provide default for 'latest_v' if not specified in spec.


0.08    2013-04-13 (SHARYANTO)

        - No functional changes. Add another FAQ item and mention more prior arts
          (sqitch, DBIx::Migration).


0.07    2013-04-12 (SHARYANTO)

        - No functional changes. Add a couple of FAQ items.


0.06    2013-04-03 (SHARYANTO)

        - No functional changes. Fix incomplete example in Synopsis.


0.05    2013-04-03 (SHARYANTO)

        - No functional changes. doc: recommend Postgres, mention how to use the
          module in a program/script, mention Database::Migrator in See Also.


0.04    2013-03-14 (SHARYANTO)

        [BUG FIXES]

        - Put creating 'meta' table inside transaction, so if 'install' phase
          fails, the meta table is not created (at least on Postgres which has
          transactional DDL).


0.03    2013-03-01 (SHARYANTO)

        [INCOMPATIBLE CHANGES]

        - Change 'sqls' argument (an array of SQL statement strings) to 'spec'
          (a hash of series of SQL statement strings). This is so that we can
          have/see 'install' which is the SQL statements for the latest version.


0.02    2013-02-28 (SHARYANTO)

        - Add error handling for when upgrade fails.

        - Wrap each upgrade within transaction block.

        - Test under Postgres.


0.01    2013-02-28 (SHARYANTO)

        - First release.
