Handle errors in perl scripts better and remove suport for $0

[dbsrgits/DBIx-Class-DeploymentHandler.git] / lib / DBIx / Class / DeploymentHandler.pm

diff --git a/lib/DBIx/Class/DeploymentHandler.pm b/lib/DBIx/Class/DeploymentHandler.pm
index 66a9ca7..41a8210 100644 (file)
--- a/lib/DBIx/Class/DeploymentHandler.pm
+++ b/lib/DBIx/Class/DeploymentHandler.pm
@@ -106,7 +106,7 @@ much more flexible than L<DBIx::Class::Schema::Versioned>, hence the use of
 L<Moose> and lots of roles.
 
 C<DBIx::Class::DeploymentHandler> itself is just a recommended set of roles
-that we think will not only work well for everyone, but will also yeild the
+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<DBIx::Class::Schema::Versioned> worked (and
@@ -180,7 +180,7 @@ You started your project and weren't using C<DBIx::Class::DeploymentHandler>?
 Lucky for you I had you in mind when I wrote this doc.
 
 First,
-L<define the version|DBIx::Class::DeploymentHandler::Intro/Sample_database>
+L<define the version|DBIx::Class::DeploymentHandler::Manual::Intro/Sample_database>
 in your main schema file (maybe using C<$VERSION>).
 
 Then you'll want to just install the version_storage:
@@ -193,7 +193,7 @@ Then you'll want to just install the 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<DBIx::Class::DeploymentHandler> like normal!