Documentation

One of the reasons for the absurd level of flexibility that DBIx::Class::DeploymentHandler is so that you can do things that we did not originally anticipate. Surprisingly, I never added a method to change the table for the version storage. That's fine though, the following recipe shows how one can do it in style:
Introduction to using DBIx::Class::DeploymentHandler with a new Catalyst Project
Introduction to DBIx::Class::DeploymentHandler

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