X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FDeploymentHandler.pm;h=df0b7eb23ef45ed118d396e4d65e9002d13de99b;hb=c13268259643c21c42fe7ee7197d66d820c0da8e;hp=89500a2b3d3f849ad7b70c31e5091c3e07cd683a;hpb=26983cf2dc0de2d512e34263c2e0c693cab4f428;p=dbsrgits%2FDBIx-Class-DeploymentHandler.git diff --git a/lib/DBIx/Class/DeploymentHandler.pm b/lib/DBIx/Class/DeploymentHandler.pm index 89500a2..df0b7eb 100644 --- a/lib/DBIx/Class/DeploymentHandler.pm +++ b/lib/DBIx/Class/DeploymentHandler.pm @@ -7,27 +7,56 @@ use Moose; extends 'DBIx::Class::DeploymentHandler::Dad'; # a single with would be better, but we can't do that # see: http://rt.cpan.org/Public/Bug/Display.html?id=46347 -with 'DBIx::Class::DeploymentHandler::WithSqltDeployMethod', - 'DBIx::Class::DeploymentHandler::WithMonotonicVersions', - 'DBIx::Class::DeploymentHandler::WithStandardVersionStorage'; +with 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => { + interface_role => 'DBIx::Class::DeploymentHandler::HandlesDeploy', + class_name => 'DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator', + delegate_name => 'deploy_method', + attributes_to_assume => [qw(schema schema_version)], + attributes_to_copy => [qw( + ignore_ddl databases script_directory sql_translator_args force_overwrite + )], + }, + 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => { + interface_role => 'DBIx::Class::DeploymentHandler::HandlesVersioning', + class_name => 'DBIx::Class::DeploymentHandler::VersionHandler::Monotonic', + delegate_name => 'version_handler', + attributes_to_assume => [qw( database_version schema_version to_version )], + }, + 'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => { + interface_role => 'DBIx::Class::DeploymentHandler::HandlesVersionStorage', + class_name => 'DBIx::Class::DeploymentHandler::VersionStorage::Standard', + delegate_name => 'version_storage', + attributes_to_assume => ['schema'], + }; with 'DBIx::Class::DeploymentHandler::WithReasonableDefaults'; sub prepare_version_storage_install { my $self = shift; - $self->prepare_resultsource_install( - $self->version_storage->version_rs->result_source - ); + $self->prepare_resultsource_install({ + result_source => $self->version_storage->version_rs->result_source + }); } sub install_version_storage { my $self = shift; - $self->install_resultsource( - $self->version_storage->version_rs->result_source - ); + my $version = (shift||{})->{version} || $self->schema_version; + + $self->install_resultsource({ + result_source => $self->version_storage->version_rs->result_source, + version => $version, + }); +} + +sub prepare_install { + $_[0]->prepare_deploy; + $_[0]->prepare_version_storage_install; } +# the following is just a hack so that ->version_storage +# won't be lazy +sub BUILD { $_[0]->version_storage } __PACKAGE__->meta->make_immutable; 1; @@ -42,12 +71,12 @@ __END__ my $s = My::Schema->connect(...); my $dh = DH->new({ - schema => $s, - databases => 'SQLite', - sqltargs => { add_drop_table => 0 }, + schema => $s, + databases => 'SQLite', + sql_translator_args => { add_drop_table => 0 }, }); - $dh->prepare_deploy; + $dh->prepare_install; $dh->install; @@ -57,12 +86,15 @@ or for upgrades: my $s = My::Schema->connect(...); my $dh = DH->new({ - schema => $s, - databases => 'SQLite', - sqltargs => { add_drop_table => 0 }, + schema => $s, + databases => 'SQLite', + sql_translator_args => { add_drop_table => 0 }, }); - $dh->prepare_upgrade(1, 2); + $dh->prepare_upgrade({ + from_version => 1, + to_version => 2, + }); $dh->upgrade; @@ -115,11 +147,11 @@ C extends L, so that's probably the first place to look when you are trying to figure out how everything works. -Next would be to look at all the roles that fill in the blanks that +Next would be to look at all the pieces that fill in the blanks that L expects to be filled. They would be -L, -L, -L, and +L, +L, +L, and L. =method prepare_version_storage_install @@ -129,6 +161,13 @@ L. Creates the needed C<.sql> file to install the version storage and not the rest of the tables +=method prepare_install + + $dh->prepare_install + +First prepare all the tables to be installed and the prepare just the version +storage + =method install_version_storage $dh->install_version_storage @@ -140,10 +179,10 @@ Install the version storage and not the rest of the tables You started your project and weren't using C? Lucky for you I had you in mind when I wrote this doc. -First off, you'll want to just install the version_storage: +First off, you'll want to just install the C: my $s = My::Schema->connect(...); - my $dh = DBIx::Class::DeploymentHandler({ schema => $s }); + my $dh = DBIx::Class::DeploymentHandler->({ schema => $s }); $dh->prepare_version_storage_install; $dh->install_version_storage; @@ -152,7 +191,22 @@ Then set your database version: $dh->add_database_version({ version => $s->version }); -Now you should be able to use DBIx::Class::DeploymentHandler like normal! +Now you should be able to use C like normal! + +=head1 LOGGING + +This is a complex tool, and because of that sometimes you'll want to see +what exactly is happening. The best way to do that is to use the built in +logging functionality. It the standard six log levels; C, C, +C, C, C, and C. Most of those are pretty self +explanatory. Generally a safe level to see what all is going on is debug, +which will give you everything except for the exact SQL being run. + +To enable the various logging levels all you need to do is set an environment +variables: C, C, C, C, +C, and C. Each level can be set on it's own, +but the default is the first three on and the last three off, and the levels +cascade, so if you turn on trace the rest will turn on automatically. =head1 DONATIONS