package DBIx::Class::DeploymentHandler::HandlesVersioning; {
$DBIx::Class::DeploymentHandler::HandlesVersioning::VERSION =
'0.002204'; } use Moose::Role; # ABSTRACT: Interface for version
methods requires 'next_version_set'; requires
'previous_version_set'; 1; # vim: ts=2 sw=2 expandtab __END__
=pod =head1 NAME
DBIx::Class::DeploymentHandler::HandlesVersioning - Interface
for version methods =head1 DESCRIPTION Typically a
VersionHandler will take a C and yeild an iterator of L.
Typically a call to a VersionHandler's L with a C of 1 and a C
of 5 will iterate over something like the following: [1, 2] [2,
3] [3, 4] [4, 5] undef or maybe just [1, 5] undef Really how the
L are arranged is up to the VersionHandler being used. In some
cases users will not want versions to have inherent "previous
versions," which is why the version set is an C. In those cases
the user should opt to returning merely the version that the
database is being upgraded to in each step. One idea that has
been suggested to me has been to have