1 package DBIx::Class::DeploymentHandler;
3 # ABSTRACT: Extensible DBIx::Class deployment
7 extends 'DBIx::Class::DeploymentHandler::Dad';
8 # a single with would be better, but we can't do that
9 # see: http://rt.cpan.org/Public/Bug/Display.html?id=46347
10 with 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => {
11 interface_role => 'DBIx::Class::DeploymentHandler::HandlesDeploy',
12 class_name => 'DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator',
13 delegate_name => 'deploy_method',
14 attributes_to_assume => [qw(schema schema_version)],
15 attributes_to_copy => [qw(
16 ignore_ddl databases script_directory sql_translator_args force_overwrite
19 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => {
20 interface_role => 'DBIx::Class::DeploymentHandler::HandlesVersioning',
21 class_name => 'DBIx::Class::DeploymentHandler::VersionHandler::Monotonic',
22 delegate_name => 'version_handler',
23 attributes_to_assume => [qw( database_version schema_version to_version )],
25 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => {
26 interface_role => 'DBIx::Class::DeploymentHandler::HandlesVersionStorage',
27 class_name => 'DBIx::Class::DeploymentHandler::VersionStorage::Standard',
28 delegate_name => 'version_storage',
29 attributes_to_assume => ['schema'],
31 with 'DBIx::Class::DeploymentHandler::WithReasonableDefaults';
33 sub prepare_version_storage_install {
36 $self->prepare_resultsource_install({
37 result_source => $self->version_storage->version_rs->result_source
41 sub install_version_storage {
44 my $version = (shift||{})->{version} || $self->schema_version;
46 $self->install_resultsource({
47 result_source => $self->version_storage->version_rs->result_source,
53 $_[0]->prepare_deploy;
54 $_[0]->prepare_version_storage_install;
57 # the following is just a hack so that ->version_storage
59 sub BUILD { $_[0]->version_storage }
60 __PACKAGE__->meta->make_immutable;
62 sub dev_version_instaled { shift->database_version eq 'DEV' }
65 sub install_dev_version {
66 my ($self, $extra) = @_;
68 die 'roll back existing dev version before installing a new dev version'
69 if $self->dev_version_installed;
71 my $from_schema = do {
72 my $t = SQL::Translator->new({
75 parser => 'SQL::Translator::Parser::YAML',
77 $t->translate($self->deploy_method->_ddl_protoschema_produce_filename(
78 $self->database_version, $self->script_directory
84 my $t = SQL::Translator->new({
85 parser => 'SQL::Translator::Parser::DBIx::Class',
87 package => $self->schema,
90 $t->translate or die $t->error;
94 my $db = $self->deploy_method->storage->sqlt_type;
96 my @up = [SQL::Translator::Diff::schema_diff(
102 my @down = [SQL::Translator::Diff::schema_diff(
108 $self->deploy_method->_run_sql_array(\@up);
110 $self->version_storage->version_rs->create({
113 downgrade_sql => \@down,
118 sub remove_dev_version {
119 my ($self, $extra) = @_;
121 die 'no dev version installed to remove'
122 unless $self->dev_version_installed;
124 my ($dev_data, $to_version) = $self->version_storage
127 order_by => { -desc => 'id' },
131 $self->deploy_method->_run_sql_array(\@sql_to_run);
133 $self->version_storage->version_rs->create({
134 version => $to_version->version,
135 upgrade_sql => \@sql_to_run,
136 downgrade_sql => [], # not meant to be "reverted"
143 #vim: ts=2 sw=2 expandtab
149 use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
150 my $s = My::Schema->connect(...);
154 databases => 'SQLite',
155 sql_translator_args => { add_drop_table => 0 },
158 $dh->prepare_install;
164 use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
165 my $s = My::Schema->connect(...);
169 databases => 'SQLite',
170 sql_translator_args => { add_drop_table => 0 },
173 $dh->prepare_upgrade({
182 C<DBIx::Class::DeploymentHandler> is, as its name suggests, a tool for
183 deploying and upgrading databases with L<DBIx::Class>. It is designed to be
184 much more flexible than L<DBIx::Class::Schema::Versioned>, hence the use of
185 L<Moose> and lots of roles.
187 C<DBIx::Class::DeploymentHandler> itself is just a recommended set of roles
188 that we think will not only work well for everyone, but will also yield the
189 best overall mileage. Each role it uses has its own nuances and
190 documentation, so I won't describe all of them here, but here are a few of the
191 major benefits over how L<DBIx::Class::Schema::Versioned> worked (and
192 L<DBIx::Class::DeploymentHandler::Deprecated> tries to maintain compatibility
199 Downgrades in addition to upgrades.
203 Multiple sql files files per upgrade/downgrade/install.
207 Perl scripts allowed for upgrade/downgrade/install.
211 Just one set of files needed for upgrade, unlike before where one might need
212 to generate C<factorial(scalar @versions)>, which is just silly.
220 That's really just a taste of some of the differences. Check out each role for
223 =head1 WHERE IS ALL THE DOC?!
225 C<DBIx::Class::DeploymentHandler> extends
226 L<DBIx::Class::DeploymentHandler::Dad>, so that's probably the first place to
227 look when you are trying to figure out how everything works.
229 Next would be to look at all the pieces that fill in the blanks that
230 L<DBIx::Class::DeploymentHandler::Dad> expects to be filled. They would be
231 L<DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator>,
232 L<DBIx::Class::DeploymentHandler::VersionHandler::Monotonic>,
233 L<DBIx::Class::DeploymentHandler::VersionStorage::Standard>, and
234 L<DBIx::Class::DeploymentHandler::WithReasonableDefaults>.
236 =method prepare_version_storage_install
238 $dh->prepare_version_storage_install
240 Creates the needed C<.sql> file to install the version storage and not the rest
243 =method prepare_install
247 First prepare all the tables to be installed and the prepare just the version
250 =method install_version_storage
252 $dh->install_version_storage
254 Install the version storage and not the rest of the tables
258 You started your project and weren't using C<DBIx::Class::DeploymentHandler>?
259 Lucky for you I had you in mind when I wrote this doc.
262 L<define the version|DBIx::Class::DeploymentHandler::Intro/Sample_database>
263 in your main schema file (maybe using C<$VERSION>).
265 Then you'll want to just install the version_storage:
267 my $s = My::Schema->connect(...);
268 my $dh = DBIx::Class::DeploymentHandler->new({ schema => $s });
270 $dh->prepare_version_storage_install;
271 $dh->install_version_storage;
273 Then set your database version:
275 $dh->add_database_version({ version => $s->version });
277 Now you should be able to use C<DBIx::Class::DeploymentHandler> like normal!
281 This is a complex tool, and because of that sometimes you'll want to see
282 what exactly is happening. The best way to do that is to use the built in
283 logging functionality. It the standard six log levels; C<fatal>, C<error>,
284 C<warn>, C<info>, C<debug>, and C<trace>. Most of those are pretty self
285 explanatory. Generally a safe level to see what all is going on is debug,
286 which will give you everything except for the exact SQL being run.
288 To enable the various logging levels all you need to do is set an environment
289 variables: C<DBICDH_FATAL>, C<DBICDH_ERROR>, C<DBICDH_WARN>, C<DBICDH_INFO>,
290 C<DBICDH_DEBUG>, and C<DBICDH_TRACE>. Each level can be set on its own,
291 but the default is the first three on and the last three off, and the levels
292 cascade, so if you turn on trace the rest will turn on automatically.
296 If you'd like to thank me for the work I've done on this module, don't give me
297 a donation. I spend a lot of free time creating free software, but I do it
300 Instead, consider donating to someone who might actually need it. Obviously
301 you should do research when donating to a charity, so don't just take my word
302 on this. I like Children's Survival Fund:
303 L<http://www.childrenssurvivalfund.org>, but there are a host of other
304 charities that can do much more good than I will with your money.