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->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) = @{$self->upgrade_single_step($version_list)||[]};
53 $self->add_database_version({
54 version => $version_list->[-1],
56 upgrade_sql => $upgrade_sql,
63 while ( my $version_list = $self->previous_version_set ) {
64 $self->downgrade_single_step($version_list);
66 # do we just delete a row here? I think so but not sure
67 $self->delete_database_version({ version => $version_list->[-1] });
71 method backup { $self->storage->backup($self->backup_directory) }
73 __PACKAGE__->meta->make_immutable;
77 # vim: ts=2 sw=2 expandtab
85 The L<DBIx::Class::Schema> (B<required>) that is used to talk to the database
88 =attr backup_directory
90 The directory where backups are stored
94 The version (defaults to schema's version) to migrate the database to
100 Deploys the current schema into the database. Populates C<version_storage> with
101 C<version> and C<ddl>.
103 B<Note>: you typically need to call C<< $dh->prepare_deploy >> before you call
106 B<Note>: you cannot install on top of an already installed database
112 Upgrades the database one step at a time till L</next_version_set>
113 returns C<undef>. Each upgrade step will add a C<version>, C<ddl>, and
114 C<upgrade_sql> to the version storage (if C<ddl> and/or C<upgrade_sql> are
115 returned from L</upgrade_single_step>.
121 Downgrades the database one step at a time till L</previous_version_set>
122 returns C<undef>. Each downgrade step will delete a C<version> from the
129 Simply calls backup on the C<< $schema->storage >>, passing in
130 C<< $self->backup_directory >> as an argument. Please test yourself before
131 assuming it will work.
133 =head1 METHODS THAT ARE REQUIRED IN SUBCLASSES
137 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/deploy>.
139 =head2 version_storage_is_installed
141 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/version_storage_is_installed>.
143 =head2 add_database_version
145 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/add_database_version>.
147 =head2 delete_database_version
149 See L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/delete_database_version>.
151 =head2 next_version_set
153 See L<DBIx::Class::DeploymentHandler::HandlesVersioning/next_version_set>.
155 =head2 previous_version_set
157 See L<DBIx::Class::DeploymentHandler::HandlesVersioning/previous_version_set>.
159 =head2 upgrade_single_step
161 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/upgrade_single_step>.
163 =head2 downgrade_single_step
165 See L<DBIx::Class::DeploymentHandler::HandlesDeploy/downgrade_single_step>.
167 =head1 ORTHODOX METHODS
169 These methods are not actually B<required> as things will probably still work
170 if you don't implement them, but if you want your subclass to get along with
171 other subclasses (or more likely, tools made to use another subclass), you
172 should probably implement these too, even if they are no-ops.
174 =head2 database_version
176 see L<DBIx::Class::DeploymentHandler::HandlesVersionStorage/database_version>
178 =head2 prepare_deploy
180 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_deploy>
182 =head2 prepare_resultsource_install
184 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_resultsource_install>
186 =head2 install_resultsource
188 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/install_resultsource>
190 =head2 prepare_upgrade
192 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_upgrade>
194 =head2 prepare_downgrade
196 see L<DBIx::Class::DeploymentHandler::HandlesDeploy/prepare_downgrade>
200 All of the methods mentioned in L</METHODS THAT ARE REQUIRED IN SUBCLASSES> and
201 L</ORTHODOX METHODS> can be implemented in any fashion you choose. In the
202 spirit of code reuse I have used roles to implement them in my two subclasses,
203 L<DBIx::Class::DeploymentHandler> and
204 L<DBIx::Class::DeploymentHandler::Deprecated>, but you are free to implement
205 them entirely in a subclass if you so choose to.
207 For in-depth documentation on how methods are supposed to work, see the roles
208 L<DBIx::Class::DeploymentHandler::HandlesDeploy>,
209 L<DBIx::Class::DeploymentHandler::HandlesVersioning>, and
210 L<DBIx::Class::DeploymentHandler::HandlesVersionStorage>.