doc for ::Dad and fix a tiny bug
[dbsrgits/DBIx-Class-DeploymentHandler.git] / lib / DBIx / Class / DeploymentHandler.pm
1 package DBIx::Class::DeploymentHandler;
2
3 use Moose;
4
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';
12
13 sub prepare_version_storage_install {
14   my $self = shift;
15
16   $self->prepare_resultsource_install(
17     $self->version_storage->version_rs->result_source
18   );
19 }
20
21 sub install_version_storage {
22   my $self = shift;
23
24   $self->install_resultsource(
25     $self->version_storage->version_rs->result_source
26   );
27 }
28
29 __PACKAGE__->meta->make_immutable;
30
31 1;
32
33 __END__
34
35 =SYNOPSIS
36
37  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
38  my $s = My::Schema->connect(...);
39
40  my $dh = DH->new({
41    schema => $s,
42    databases => 'SQLite',
43    sqltargs => { add_drop_table => 0 },
44  });
45
46  $dh->prepare_install;
47
48  $dh->install;
49
50 or for upgrades:
51
52  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
53  my $s = My::Schema->connect(...);
54
55  my $dh = DH->new({
56    schema => $s,
57    databases => 'SQLite',
58    sqltargs => { add_drop_table => 0 },
59  });
60
61  $dh->prepare_upgrade(1, 2);
62
63  $dh->upgrade;
64
65 =head1 DESCRIPTION
66
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.
71
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
78 with):
79
80 =over
81
82 =over
83
84 =item *
85
86 Downgrades in addition to upgrades.
87
88 =item *
89
90 Multiple sql files files per upgrade/downgrade/install.
91
92 =item *
93
94 Perl scripts allowed for upgrade/downgrade/install.
95
96 =item *
97
98 Just one set of files needed for upgrade, unlike before where one might need
99 to generate C<factorial(scalar @versions)>, which is just silly.
100
101 =item *
102
103 And much, much more!
104
105 =back
106
107 That's really just a taste of some of the differences.  Check out each role for
108 all the details.
109
110 =head1 WHERE IS ALL THE DOC?!
111
112 C<DBIx::Class::DeploymentHandler> extends
113 L<DBIx::Class::DeploymentHandler::Dad>, so that's probably the first place to
114 look when you are trying to figure out how everything works.
115
116 Next would be to look at all the roles that fill in the blanks that
117 L<DBIx::Class::DeploymentHandler::Dad> expects to be filled.  They would be
118 L<DBIx::Class::DeploymentHandler::WithSqltDeployMethod>,
119 L<DBIx::Class::DeploymentHandler::WithMonotonicVersions>,
120 L<DBIx::Class::DeploymentHandler::WithStandardVersionStorage>, and
121 L<DBIx::Class::DeploymentHandler::WithReasonableDefaults>.
122
123 =method prepare_version_storage_install
124
125  $dh->prepare_version_storage_install
126
127 Creates the needed C<.sql> file to install the version storage and not the rest
128 of the tables
129
130 =method install_version_storage
131
132  $dh->install_version_storage
133
134 Install the version storage and not the rest of the tables
135
136 __END__
137
138 vim: ts=2 sw=2 expandtab