X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FDeploymentHandler.pm;h=b7d1d6ff74f71eaa66b0885b4e55dba50fbec24c;hb=97aa9a748e07c9e5875d56bd7d6554e481911c5d;hp=a30ec4d66eca312d792aaf8eef3a7eaae4c92fc7;hpb=4f73e4ac36aa022797c6a9dca0afb98f82a0c38c;p=dbsrgits%2FDBIx-Class-DeploymentHandler.git diff --git a/lib/DBIx/Class/DeploymentHandler.pm b/lib/DBIx/Class/DeploymentHandler.pm index a30ec4d..b7d1d6f 100644 --- a/lib/DBIx/Class/DeploymentHandler.pm +++ b/lib/DBIx/Class/DeploymentHandler.pm @@ -8,47 +8,55 @@ 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::WithApplicatorDumple' => { - interface_role => 'DBIx::Class::DeploymentHandler::HandlesDeploy', - class_name => 'DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator', - delegate_name => 'deploy_method', - attributes_to_assume => ['schema'], - attributes_to_copy => [qw( databases upgrade_directory sql_translator_args )], - }, - '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'], - }; + 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; + $_[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; @@ -83,20 +91,23 @@ or for upgrades: sql_translator_args => { add_drop_table => 0 }, }); - $dh->prepare_upgrade(1, 2); + $dh->prepare_upgrade({ + from_version => 1, + to_version => 2, + }); $dh->upgrade; =head1 DESCRIPTION -C is, as it's name suggests, a tool for +C is, as its name suggests, a tool for deploying and upgrading databases with L. It is designed to be much more flexible than L, hence the use of L and lots of roles. C itself is just a recommended set of roles -that we think will not only work well for everyone, but will also yeild the -best overall mileage. Each role it uses has it's own nuances and +that we think will not only work well for everyone, but will also yield the +best overall mileage. Each role it uses has its own nuances and documentation, so I won't describe all of them here, but here are a few of the major benefits over how L worked (and L tries to maintain compatibility @@ -136,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 @@ -168,20 +179,39 @@ 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 C: +First, +L +in your main schema file (maybe using C<$VERSION>). + +Then you'll want to just install the version_storage: my $s = My::Schema->connect(...); - my $dh = DBIx::Class::DeploymentHandler({ schema => $s }); + my $dh = DBIx::Class::DeploymentHandler->new({ schema => $s }); $dh->prepare_version_storage_install; $dh->install_version_storage; Then set your database version: - $dh->add_database_version({ version => $s->version }); + $dh->add_database_version({ version => $s->schema_version }); 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 its 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 If you'd like to thank me for the work I've done on this module, don't give me @@ -190,6 +220,8 @@ because I love it. Instead, consider donating to someone who might actually need it. Obviously you should do research when donating to a charity, so don't just take my word -on this. I like Children's Survival Fund: -L, but there are a host of other +on this. I like Matthew 25: Ministries: +L, but there are a host of other charities that can do much more good than I will with your money. +(Third party charity info here: +L