1 package DBIx::Class::DeploymentHandler;
5 extends 'DBIx::Class::DeploymentHandler::Dad';
6 # a single with would be better, but we can't do that
7 # see: http://rt.cpan.org/Public/Bug/Display.html?id=46347
8 with 'DBIx::Class::DeploymentHandler::WithSqltDeployMethod',
9 'DBIx::Class::DeploymentHandler::WithMonotonicVersions',
10 'DBIx::Class::DeploymentHandler::WithStandardVersionStorage';
11 with 'DBIx::Class::DeploymentHandler::WithReasonableDefaults';
13 sub prepare_version_storage_install {
16 $self->prepare_resultsource_install(
17 $self->version_storage->version_rs->result_source
21 sub install_version_storage {
24 $self->install_resultsource(
25 $self->version_storage->version_rs->result_source
29 __PACKAGE__->meta->make_immutable;
37 use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
38 my $s = My::Schema->connect(...);
42 databases => 'SQLite',
43 sqltargs => { add_drop_table => 0 },
52 use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
53 my $s = My::Schema->connect(...);
57 databases => 'SQLite',
58 sqltargs => { add_drop_table => 0 },
61 $dh->prepare_upgrade(1, 2);
67 C<DBIx::Class::DeploymentHandler> is, as it's name suggests, a tool for
68 deploying and upgrading databases with L<DBIx::Class>. It is designed to be
69 much more flexible than L<DBIx::Class::Schema::Versioned>, hence the use of
70 L<Moose> and lots of roles.
72 C<DBIx::Class::DeploymentHandler> itself is just a recommended set of roles
73 that we think will not only work well for everyone, but will also yeild the
74 best overall mileage. Each role it uses has it's own nuances and
75 documentation, so I won't describe all of them here, but here are a few of the
76 major benefits over how L<DBIx::Class::Schema::Versioned> worked (and
77 L<DBIx::Class::DeploymentHandler::Deprecated> tries to maintain compatibility
84 Downgrades in addition to upgrades.
88 Multiple sql files files per upgrade/downgrade/install.
92 Perl scripts allowed for upgrade/downgrade/install.
96 Just one set of files needed for upgrade, unlike before where one might need
97 to generate C<factorial(scalar @versions)>, which is just silly.
105 That's really just a taste of some of the differences. Check out each role for
108 =head1 WHERE IS ALL THE DOC?!
110 C<DBIx::Class::DeploymentHandler> extends
111 L<DBIx::Class::DeploymentHandler::Dad>, so that's probably the first place to
112 look when you are trying to figure out how everything works.
114 Next would be to look at all the roles that fill in the blanks that
115 L<DBIx::Class::DeploymentHandler::Dad> expects to be filled. They would be
116 L<DBIx::Class::DeploymentHandler::WithSqltDeployMethod>,
117 L<DBIx::Class::DeploymentHandler::WithMonotonicVersions>,
118 L<DBIx::Class::DeploymentHandler::WithStandardVersionStorage>, and
119 L<DBIx::Class::DeploymentHandler::WithReasonableDefaults>.
121 =method prepare_version_storage_install
123 $dh->prepare_version_storage_install
125 Creates the needed C<.sql> file to install the version storage and not the rest
128 =method install_version_storage
130 $dh->install_version_storage
132 Install the version storage and not the rest of the tables
136 vim: ts=2 sw=2 expandtab