Changes for version 0.001000_09 - 2010-05-15

  • Schemata is no longer required to add version checking component

Changes for version 0.001000_08 - 2010-05-11

  • Add missing dep namespace::autoclean

Changes for version 0.001000_07 - 2010-05-09

  • Downgrades swap from version and to version, so instead of up 1-2 being down 1-2, it's down 2-1, which clearly makes more sense
  • perl scripts are now just anonymous subroutines, instead of files with a single run subroutine
  • Serious changes to architecture by using MXRP instead of lots of repetitive roles

Changes for version 0.001000_06 - 2010-05-05

  • Add a bunch of boilerplate and not so boilerplate doc
  • rename sqltargs attribute to sql_translator_args

Changes for version 0.001000_05 - 2010-05-04

  • put schema_version attr in more places

Changes for version 0.001000_04 - 2010-04-27

  • schema_version is now an attr so that users can more easily force the version of the schema
  • add prepare_install method which installs everything as well as the version storage

Changes for version 0.001000_03 - 2010-04-20

  • bump File::Path dep

Changes for version 0.001000_02 - 2010-04-19

  • add autodie as dep

Changes for version 0.001000_01

  • initial dev release

Modules

Extensible DBIx::Class deployment
Parent class for DeploymentHandlers
Manage your SQL and Perl migrations in nicely laid out directories
(DEPRECATED) Use this if you are stuck in the past
(DEPRECATED) Use this if you are stuck in the past
Interface for deploy methods
Interface for version storage methods
Types internal to DBIx::Class::DeploymentHandler
Define your own list of versions to use for migrations
(DEPRECATED) Use this if you are stuck in the past
(DEPRECATED) Attach this component to your schema to ensure you stay up to date
(DEPRECATED) The old way to store versions in the database
(DEPRECATED) Predefined searches to find what you want from the version storage
Version storage that does the normal stuff
Attach this component to your schema to ensure you stay up to date
The typical way to store versions in the database
Predefined searches to find what you want from the version storage
Make default arguments to a few methods sensible