lib/DBIx/Class/DeploymentHandler.pm

   1 package DBIx::Class::DeploymentHandler;
   2
   3 # ABSTRACT: Extensible DBIx::Class deployment
   4
   5 use Moose;
   6
   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::WithSqltDeployMethod',
  11      'DBIx::Class::DeploymentHandler::WithMonotonicVersions',
  12      'DBIx::Class::DeploymentHandler::WithStandardVersionStorage';
  13 with 'DBIx::Class::DeploymentHandler::WithReasonableDefaults';
  14
  15 sub prepare_version_storage_install {
  16   my $self = shift;
  17
  18   $self->prepare_resultsource_install(
  19     $self->version_storage->version_rs->result_source
  20   );
  21 }
  22
  23 sub install_version_storage {
  24   my $self = shift;
  25
  26   $self->install_resultsource(
  27     $self->version_storage->version_rs->result_source
  28   );
  29 }
  30
  31 __PACKAGE__->meta->make_immutable;
  32
  33 1;
  34
  35 #vim: ts=2 sw=2 expandtab
  36
  37 __END__
  38
  39 =head1 SYNOPSIS
  40
  41  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
  42  my $s = My::Schema->connect(...);
  43
  44  my $dh = DH->new({
  45    schema => $s,
  46    databases => 'SQLite',
  47    sqltargs => { add_drop_table => 0 },
  48  });
  49
  50  $dh->prepare_install;
  51
  52  $dh->install;
  53
  54 or for upgrades:
  55
  56  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
  57  my $s = My::Schema->connect(...);
  58
  59  my $dh = DH->new({
  60    schema => $s,
  61    databases => 'SQLite',
  62    sqltargs => { add_drop_table => 0 },
  63  });
  64
  65  $dh->prepare_upgrade(1, 2);
  66
  67  $dh->upgrade;
  68
  69 =head1 DESCRIPTION
  70
  71 C<DBIx::Class::DeploymentHandler> is, as it's name suggests, a tool for
  72 deploying and upgrading databases with L<DBIx::Class>.  It is designed to be
  73 much more flexible than L<DBIx::Class::Schema::Versioned>, hence the use of
  74 L<Moose> and lots of roles.
  75
  76 C<DBIx::Class::DeploymentHandler> itself is just a recommended set of roles
  77 that we think will not only work well for everyone, but will also yeild the
  78 best overall mileage.  Each role it uses has it's own nuances and
  79 documentation, so I won't describe all of them here, but here are a few of the
  80 major benefits over how L<DBIx::Class::Schema::Versioned> worked (and
  81 L<DBIx::Class::DeploymentHandler::Deprecated> tries to maintain compatibility
  82 with):
  83
  84 =over
  85
  86 =item *
  87
  88 Downgrades in addition to upgrades.
  89
  90 =item *
  91
  92 Multiple sql files files per upgrade/downgrade/install.
  93
  94 =item *
  95
  96 Perl scripts allowed for upgrade/downgrade/install.
  97
  98 =item *
  99
 100 Just one set of files needed for upgrade, unlike before where one might need
 101 to generate C<factorial(scalar @versions)>, which is just silly.
 102
 103 =item *
 104
 105 And much, much more!
 106
 107 =back
 108
 109 That's really just a taste of some of the differences.  Check out each role for
 110 all the details.
 111
 112 =head1 WHERE IS ALL THE DOC?!
 113
 114 C<DBIx::Class::DeploymentHandler> extends
 115 L<DBIx::Class::DeploymentHandler::Dad>, so that's probably the first place to
 116 look when you are trying to figure out how everything works.
 117
 118 Next would be to look at all the roles that fill in the blanks that
 119 L<DBIx::Class::DeploymentHandler::Dad> expects to be filled.  They would be
 120 L<DBIx::Class::DeploymentHandler::WithSqltDeployMethod>,
 121 L<DBIx::Class::DeploymentHandler::WithMonotonicVersions>,
 122 L<DBIx::Class::DeploymentHandler::WithStandardVersionStorage>, and
 123 L<DBIx::Class::DeploymentHandler::WithReasonableDefaults>.
 124
 125 =method prepare_version_storage_install
 126
 127  $dh->prepare_version_storage_install
 128
 129 Creates the needed C<.sql> file to install the version storage and not the rest
 130 of the tables
 131
 132 =method install_version_storage
 133
 134  $dh->install_version_storage
 135
 136 Install the version storage and not the rest of the tables
 137
 138 =head1 THIS SUCKS
 139
 140 You started your project and weren't using DBICDH?  FOOL!  Lucky for you I had
 141 you in mind when I wrote this doc <3
 142
 143 First off, you'll want to just install the version_storage:
 144
 145  my $s = My::Schema->connect(...);
 146  my $dh = DeployHandler({ schema => $s });
 147
 148  $dh->prepare_version_storage_install;
 149  $dh->install_version_storage;
 150
 151 Then, bump your schema version, and you can use DBICDH like normal!