From: Arthur Axel 'fREW' Schmidt <frioux@gmail.com>
Date: Thu, 24 Feb 2011 04:45:11 +0000 (-0600)
Subject: fix minor issues reported on RT
X-Git-Tag: v0.001005~4
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits%2FDBIx-Class-DeploymentHandler.git;a=commitdiff_plain;h=8b810386d7e04607a8c85ef130c5a3be7e5a00d2;hp=04a771987410a757f0087fe1375eac612850c785

fix minor issues reported on RT
---

diff --git a/lib/DBIx/Class/DeploymentHandler.pm b/lib/DBIx/Class/DeploymentHandler.pm
index df0b7eb..66a9ca7 100644
--- a/lib/DBIx/Class/DeploymentHandler.pm
+++ b/lib/DBIx/Class/DeploymentHandler.pm
@@ -100,14 +100,14 @@ or for upgrades:
 
 =head1 DESCRIPTION
 
-C<DBIx::Class::DeploymentHandler> is, as it's name suggests, a tool for
+C<DBIx::Class::DeploymentHandler> is, as its name suggests, a tool for
 deploying and upgrading databases with L<DBIx::Class>.  It is designed to be
 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
-best overall mileage.  Each role it uses has it's own nuances and
+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
 L<DBIx::Class::DeploymentHandler::Deprecated> tries to maintain compatibility
@@ -179,10 +179,14 @@ Install the version storage and not the rest of the tables
 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 off, you'll want to just install the C<version_storage>:
+First,
+L<define the version|DBIx::Class::DeploymentHandler::Intro/Sample_database>
+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;
@@ -204,7 +208,7 @@ 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<DBICDH_FATAL>, C<DBICDH_ERROR>, C<DBICDH_WARN>, C<DBICDH_INFO>,
-C<DBICDH_DEBUG>, and C<DBICDH_TRACE>.  Each level can be set on it's own,
+C<DBICDH_DEBUG>, and C<DBICDH_TRACE>.  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.