1 package DBIx::Class::DeploymentHandler::Dad;
3 # ABSTRACT: Parent class for DeploymentHandlers
6 use Method::Signatures::Simple;
7 require DBIx::Class::Schema; # loaded for type constraint
8 use Carp::Clan '^DBIx::Class::DeploymentHandler';
11 isa => 'DBIx::Class::Schema',
16 has backup_directory => (
19 predicate => 'has_backup_directory',
27 sub _build_to_version { $_[0]->schema_version }
29 has schema_version => (
34 sub _build_schema_version { $_[0]->schema->schema_version }
37 croak 'Install not possible as versions table already exists in database'
38 if $self->version_storage_is_installed;
40 my $ddl = $self->deploy;
42 $self->add_database_version({
43 version => $self->to_version,
50 while ( my $version_list = $self->next_version_set ) {
51 my ($ddl, $upgrade_sql) = @{
52 $self->upgrade_single_step({ version_set => $version_list })
55 $self->add_database_version({
56 version => $version_list->[-1],
58 upgrade_sql => $upgrade_sql,
65 while ( my $version_list = $self->previous_version_set ) {
66 $self->downgrade_single_step({ version_set => $version_list });
68 # do we just delete a row here? I think so but not sure
69 $self->delete_database_version({ version => $version_list->[-1] });
73 method backup { $self->storage->backup($self->backup_directory) }
75 __PACKAGE__->meta->make_immutable;
79 # vim: ts=2 sw=2 expandtab
87 The L<DBIx::Class::Schema> (B<required>) that is used to talk to the database
92 The version that the schema is currently at. Defaults to
93 C<< $self->schema->schema_version >>.
95 =attr backup_directory
97 The directory where backups are stored
101 The version (defaults to schema's version) to migrate the database to
107 Deploys the current schema into the database. Populates C<version_storage> with
108 C<version> and C<ddl>.
110 B<Note>: you typically need to call C<< $dh->prepare_deploy >> before you call
113 B<Note>: you cannot install on top of an already installed database
119 Upgrades the database one step at a time till L</next_version_set>
120 returns C<undef>. Each upgrade step will add a C<version>, C<ddl>, and
121 C<upgrade_sql> to the version storage (if C<ddl> and/or C<upgrade_sql> are
122 returned from L</upgrade_single_step>.
128 Downgrades the database one step at a time till L</previous_version_set>
129 returns C<undef>. Each downgrade step will delete a C<version> from the
136 Simply calls backup on the C<< $schema->storage >>, passing in
137 C<< $self->backup_directory >> as an argument. Please test yourself before
138 assuming it will work.
140 =head1 METHODS THAT ARE REQUIRED IN SUBCLASSES
144 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/deploy>.
146 =head2 version_storage_is_installed
148 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/version_storage_is_installed>.
150 =head2 add_database_version
152 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/add_database_version>.
154 =head2 delete_database_version
156 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/delete_database_version>.
158 =head2 next_version_set
160 See L<DBIx::Class::DeploymentHandler::HandlesVersioning/next_version_set>.
162 =head2 previous_version_set
164 See L<DBIx::Class::DeploymentHandler::HandlesVersioning/previous_version_set>.
166 =head2 upgrade_single_step
168 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/upgrade_single_step>.
170 =head2 downgrade_single_step
172 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/downgrade_single_step>.
174 =head1 ORTHODOX METHODS
176 These methods are not actually B<required> as things will probably still work
177 if you don't implement them, but if you want your subclass to get along with
178 other subclasses (or more likely, tools made to use another subclass), you
179 should probably implement these too, even if they are no-ops.
181 =head2 database_version
183 see L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/database_version>
185 =head2 prepare_deploy
187 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_deploy>
189 =head2 prepare_resultsource_install
191 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_resultsource_install>
193 =head2 install_resultsource
195 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/install_resultsource>
197 =head2 prepare_upgrade
199 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_upgrade>
201 =head2 prepare_downgrade
203 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_downgrade>
207 All of the methods mentioned in L</METHODS THAT ARE REQUIRED IN SUBCLASSES> and
208 L</ORTHODOX METHODS> can be implemented in any fashion you choose. In the
209 spirit of code reuse I have used roles to implement them in my two subclasses,
210 L<DBIx::Class::DeploymentHandler> and
211 L<DBIx::Class::DeploymentHandler::Deprecated>, but you are free to implement
212 them entirely in a subclass if you so choose to.
214 For in-depth documentation on how methods are supposed to work, see the roles
215 L<DBIx::Class::DeploymentHandler::HandlesDeploy>,
216 L<DBIx::Class::DeploymentHandler::HandlesVersioning>, and
217 L<DBIx::Class::DeploymentHandler::HandlesVersionStorage>.