Correct the directory name for the populate script

[dbsrgits/DBIx-Class-DeploymentHandler.git] / lib / DBIx / Class / DeploymentHandler / Manual / Intro.pod

diff --git a/lib/DBIx/Class/DeploymentHandler/Manual/Intro.pod b/lib/DBIx/Class/DeploymentHandler/Manual/Intro.pod
index 1ca76f1..a214e73 100644 (file)
--- a/lib/DBIx/Class/DeploymentHandler/Manual/Intro.pod
+++ b/lib/DBIx/Class/DeploymentHandler/Manual/Intro.pod
@@ -43,7 +43,7 @@ this makes versioning much simpler for figuring out what version is next
 Our first script, C<install.pl> reads our schema file and creates the tables
 in the database.
 
- #!perl
+ #!/usr/bin/env perl
  use strict;
  use warnings;
  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';
@@ -90,7 +90,7 @@ translated into the sql.
 
 To truly take advantage of all DBIx::Class::DeploymentHandler offers, you
 should probably be using it for population.  To do that all you need to do
-is create a file called C<dbicdh/_common/install/1/create_artists.pl>:
+is create a file called C<dbicdh/_common/deploy/1/create_artists.pl>:
 
  sub {
     my $schema = shift;
@@ -117,9 +117,15 @@ fail for logical reasons.  To be clear, if you add a column to a database and
 it is not nullable and has no default, what will the existing rows contain
 for that column?
 
+Now you need to modify the schema version in your MyDatabase::Main file to
+tell DBIx::Class::DeploymentHandler the new schema version number. You will
+want to remember the earlier advice about integer version numbers.
+
+ our $VERSION = 2;
+
 So here is our next script, C<upgrade.pl>:
 
- #!perl
+ #!/usr/bin/env perl
  use strict;
  use warnings;
  use aliased 'DBIx::Class::DeploymentHandler' => 'DH';