add some extra doc for non-integer version users

[dbsrgits/DBIx-Class-DeploymentHandler.git] / lib / DBIx / Class / DeploymentHandler / Cookbook / CustomResultSource.pod

diff --git a/lib/DBIx/Class/DeploymentHandler/Cookbook/CustomResultSource.pod b/lib/DBIx/Class/DeploymentHandler/Cookbook/CustomResultSource.pod
index fed4a9f..2f1b79d 100644 (file)
--- a/lib/DBIx/Class/DeploymentHandler/Cookbook/CustomResultSource.pod
+++ b/lib/DBIx/Class/DeploymentHandler/Cookbook/CustomResultSource.pod
@@ -1,3 +1,5 @@
+package DBIx::Class::DeploymentHandler::Cookbook::CustomResultSource;
+
 =pod
 
 One of the reasons for the absurd level of flexibility that
@@ -51,7 +53,7 @@ table being set on the original result.
      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 )],
+     attributes_to_copy   => [qw( databases script_directory sql_translator_args )],
    },
    'DBIx::Class::DeploymentHandler::WithApplicatorDumple' => {
      interface_role       => 'DBIx::Class::DeploymentHandler::HandlesVersioning',
@@ -92,3 +94,9 @@ table being set on the original result.
  __PACKAGE__->meta->make_immutable;
  1;
 
+Note: if you are using decimal numbers for versioning, you should ammend
+this DeploymentHandler package, setting it's VersionHandler class_name from
+Monotonic ( which handles integer only version numbers ) to ExplicitVersions
+or DatabaseToSchemaVersions, as these handle version numbers as strings
+instead of integers.
+