@@ -2,6 +2,16 @@ Revision history for DBIx-Class-Migration.
NOTE: Date format is YEAR-MONTH-DAY
+0.046 2015-01-26 03:10:37+00:00 Europe/London
+
+ - Switch from Test::postgresql to Test::PostgreSQL
+ ( the latter is a fork of the former )
+
+0.04_5 2015-01-15 01:44:23+00:00 Europe/London
+
+ - Don't use config_dir from DBIx::Class::Fixtures as a Path::Class::Dir,
+ it no longer is one.
+
0.044 2013-20-35
- POD fixs (MidLifeXis++)
- fix probably where a --targetdir override is not probably recognized
@@ -1,4 +1,4 @@
-This software is copyright (c) 2013 by John Napiorkowski.
+This software is copyright (c) 2015 by John Napiorkowski.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
@@ -12,7 +12,7 @@ b) the "Artistic License"
--- The GNU General Public License, Version 1, February 1989 ---
-This software is Copyright (c) 2013 by John Napiorkowski.
+This software is Copyright (c) 2015 by John Napiorkowski.
This is free software, licensed under:
@@ -22,7 +22,7 @@ This is free software, licensed under:
Version 1, February 1989
Copyright (C) 1989 Free Software Foundation, Inc.
- 51 Franklin St, Suite 500, Boston, MA 02110-1335 USA
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -272,7 +272,7 @@ That's all there is to it!
--- The Artistic License 1.0 ---
-This software is Copyright (c) 2013 by John Napiorkowski.
+This software is Copyright (c) 2015 by John Napiorkowski.
This is free software, licensed under:
@@ -1,3 +1,4 @@
+# This file was automatically generated by Dist::Zilla::Plugin::Manifest v5.031.
Changes
LICENSE
MANIFEST
@@ -129,14 +130,9 @@ examples/MusicBase/t/upgrade-1to2.t
examples/MusicBase/t/upgrade-2to3.t
examples/MusicBase/t/use.t
examples/MusicBase/t/web.t
-lib/.DS_Store
lib/Catalyst/TraitFor/Model/DBIC/Schema/FromMigration.pm
lib/Catalyst/TraitFor/Model/DBIC/Schema/FromMigration/_MigrationHelper.pm
-lib/DBIx/.DS_Store
-lib/DBIx/Class/.DS_Store
lib/DBIx/Class/Migration.pm
-lib/DBIx/Class/Migration/.DS_Store
-lib/DBIx/Class/Migration/.FAQ.pod.swp
lib/DBIx/Class/Migration/FAQ.pod
lib/DBIx/Class/Migration/Features.pod
lib/DBIx/Class/Migration/MySQLSandbox.pm
@@ -150,7 +146,6 @@ lib/DBIx/Class/Migration/RunScript/Trait/TargetPath.pm
lib/DBIx/Class/Migration/Sandbox.pm
lib/DBIx/Class/Migration/SchemaLoader.pm
lib/DBIx/Class/Migration/Script.pm
-lib/DBIx/Class/Migration/Script/.DS_Store
lib/DBIx/Class/Migration/Script/Help.pod
lib/DBIx/Class/Migration/Script/Help/databases.pod
lib/DBIx/Class/Migration/Script/Help/dbi_connect_attrs.pod
@@ -201,24 +196,18 @@ lib/DBIx/Class/Migration/Tutorial/Testing.pod
lib/DBIx/Class/Migration/Tutorial/ThirdMigration.pod
lib/DBIx/Class/Migration/Types.pm
lib/Test/DBIx/Class/FixtureCommand/Population.pm
-t/.DS_Store
t/.devdir
t/00-clean.t
t/help.t
t/install-version-storage.t
-t/lib/.DS_Store
-t/lib/Local/.DS_Store
t/lib/Local/Schema.pm
-t/lib/Local/Schema/.DS_Store
t/lib/Local/Schema/Result/Artist.pm
t/lib/Local/Schema/Result/ArtistCd.pm
t/lib/Local/Schema/Result/Cd.pm
t/lib/Local/Schema/Result/Country.pm
t/lib/Local/Schema/Result/Track.pm
t/lib/Local/Schema/ResultSet/Artist.pm
-t/lib/Local/v2/.DS_Store
t/lib/Local/v2/Schema.pm
-t/lib/Local/v2/Schema/.DS_Store
t/lib/Local/v2/Schema/Result/Artist.pm
t/lib/Local/v2/Schema/Result/ArtistCd.pm
t/lib/Local/v2/Schema/Result/Cd.pm
@@ -232,7 +221,6 @@ t/missing-schema-version.t
t/ordering.t
t/runscript.t
t/script.t
-t/share/.DS_Store
t/share/donotremove.txt
t/upgrade-downgrade-sqlite.t
t/use.t
@@ -3,45 +3,67 @@ abstract: 'Tools to make migrating your DBIx::Class databases easier'
author:
- 'John Napiorkowski <jjnapiork@cpan.org>'
build_requires:
- File::Path: 0
- File::Spec::Functions: 0
- Test::Most: 0
- Test::Requires: 0
+ File::Path: '0'
+ File::Spec::Functions: '0'
+ Test::Most: '0'
+ Test::Requires: '0'
configure_requires:
- ExtUtils::MakeMaker: 6.30
+ ExtUtils::MakeMaker: '0'
dynamic_config: 0
-generated_by: 'Dist::Zilla version 4.300039, CPAN::Meta::Converter version 2.132661'
+generated_by: 'Dist::Zilla version 5.031, CPAN::Meta::Converter version 2.143240'
license: perl
meta-spec:
url: http://module-build.sourceforge.net/META-spec-v1.4.html
- version: 1.4
+ version: '1.4'
name: DBIx-Class-Migration
requires:
- Class::Load: 0
- Config::MySQL: 0.02
- DBD::SQLite: 1.35
- DBIx::Class::DeploymentHandler: 0.002100
- DBIx::Class::Fixtures: 1.001016
- DBIx::Class::Schema::Loader: 0.07017
- Devel::PartialDump: 0
- File::Copy: 0
- File::Path: 0
- File::ShareDir::ProjectDistDir: 0.003001
- File::Spec: 0
- File::Temp: 0
- JSON::XS: 2.32
- Moose: 0
- MooseX::Attribute::ENV: 0.02
- MooseX::Getopt: 0.45
- MooseX::Traits::Pluggable: 0
- MooseX::Types: 0
- MooseX::Types::LoadableClass: 0
- Pod::Parser: 1.51
- SQL::Translator: 0.11010
- Text::Brew: 0
- version: 0.77
+ Class::Load: '0'
+ Config::MySQL: '0.02'
+ DBD::SQLite: '1.35'
+ DBIx::Class::DeploymentHandler: '0.002100'
+ DBIx::Class::Fixtures: '1.001016'
+ DBIx::Class::Schema::Loader: '0.07017'
+ Devel::PartialDump: '0'
+ File::Copy: '0'
+ File::Path: '0'
+ File::ShareDir::ProjectDistDir: '0.003001'
+ File::Spec: '0'
+ File::Temp: '0'
+ JSON::XS: '2.32'
+ Moose: '0'
+ MooseX::Attribute::ENV: '0.02'
+ MooseX::Getopt: '0.45'
+ MooseX::Traits::Pluggable: '0'
+ MooseX::Types: '0'
+ MooseX::Types::LoadableClass: '0'
+ Pod::Parser: '1.51'
+ SQL::Translator: '0.11010'
+ Text::Brew: '0'
+ version: '0.77'
resources:
bugtracker: https://github.com/jjn1056/DBIx-Class-Migration/issues
homepage: https://github.com/jjn1056/DBIx-Class-Migration
repository: https://github.com/jjn1056/DBIx-Class-Migration.git
-version: 0.044
+version: '0.046'
+x_contributors:
+ - 'Alan Berndt <alan@eatabrick.org>'
+ - 'Andy Gorman <andy@apacesystems.com>'
+ - 'Andy Jones <andy@broadbean.com>'
+ - 'Breno G. de Oliveira <garu@cpan.org>'
+ - 'Brian Wightman <MidLifeXis@wightmanfam.org>'
+ - 'Chris Weyl <cweyl@alumni.drew.edu>'
+ - 'chromatic <chromatic@wgz.org>'
+ - 'Fitz Elliott <felliott@virginia.edu>'
+ - 'jjn1056 <jjn1056@yahoo.com>'
+ - 'John Napiorkowski <jjn1056@yahoo.com>'
+ - 'Logan <loganbell@gmail.com>'
+ - 'Matthias Krull <mkrull@uninets.eu>'
+ - 'moltar <moltar@moltar.net>'
+ - 'Neil Bowers <neil@bowers.com>'
+ - 'Panu Ervamaa <panu.ervamaa@frantic.com>'
+ - 'Paul Johnson <paul@pjcj.net>'
+ - 'Samuel Kaufman <samuel.c.kaufman@gmail.com>'
+ - 'Samuel Kaufman <skaufman@cpan.org>'
+ - 'skaufman <sam@socialflow.com>'
+ - 'Volker Kroll <kroll@strato-rz.de>'
+ - 'Volker Kroll (vkroll) <kroll@strato-rz.de>'
@@ -1,19 +1,19 @@
+# This file was automatically generated by Dist::Zilla::Plugin::MakeMaker v5.031.
use strict;
use warnings;
-use ExtUtils::MakeMaker 6.30;
+use ExtUtils::MakeMaker;
my %WriteMakefileArgs = (
"ABSTRACT" => "Tools to make migrating your DBIx::Class databases easier",
"AUTHOR" => "John Napiorkowski <jjnapiork\@cpan.org>",
- "BUILD_REQUIRES" => {},
"CONFIGURE_REQUIRES" => {
- "ExtUtils::MakeMaker" => "6.30"
+ "ExtUtils::MakeMaker" => 0
},
"DISTNAME" => "DBIx-Class-Migration",
"EXE_FILES" => [
@@ -52,37 +52,48 @@ my %WriteMakefileArgs = (
"Test::Most" => 0,
"Test::Requires" => 0
},
- "VERSION" => "0.044",
+ "VERSION" => "0.046",
"test" => {
"TESTS" => "t/*.t"
}
);
-unless ( eval { ExtUtils::MakeMaker->VERSION(6.63_03) } ) {
- my $tr = delete $WriteMakefileArgs{TEST_REQUIRES};
- my $br = $WriteMakefileArgs{BUILD_REQUIRES};
- for my $mod ( keys %$tr ) {
- if ( exists $br->{$mod} ) {
- $br->{$mod} = $tr->{$mod} if $tr->{$mod} > $br->{$mod};
- }
- else {
- $br->{$mod} = $tr->{$mod};
- }
- }
-}
+my %FallbackPrereqs = (
+ "Class::Load" => 0,
+ "Config::MySQL" => "0.02",
+ "DBD::SQLite" => "1.35",
+ "DBIx::Class::DeploymentHandler" => "0.002100",
+ "DBIx::Class::Fixtures" => "1.001016",
+ "DBIx::Class::Schema::Loader" => "0.07017",
+ "Devel::PartialDump" => 0,
+ "ExtUtils::MakeMaker" => 0,
+ "File::Copy" => 0,
+ "File::Path" => 0,
+ "File::ShareDir::ProjectDistDir" => "0.003001",
+ "File::Spec" => 0,
+ "File::Spec::Functions" => 0,
+ "File::Temp" => 0,
+ "JSON::XS" => "2.32",
+ "Moose" => 0,
+ "MooseX::Attribute::ENV" => "0.02",
+ "MooseX::Getopt" => "0.45",
+ "MooseX::Traits::Pluggable" => 0,
+ "MooseX::Types" => 0,
+ "MooseX::Types::LoadableClass" => 0,
+ "Pod::Parser" => "1.51",
+ "SQL::Translator" => "0.11010",
+ "Test::Most" => 0,
+ "Test::Requires" => 0,
+ "Text::Brew" => 0,
+ "version" => "0.77"
+);
-unless ( eval { ExtUtils::MakeMaker->VERSION(6.56) } ) {
- my $br = delete $WriteMakefileArgs{BUILD_REQUIRES};
- my $pp = $WriteMakefileArgs{PREREQ_PM};
- for my $mod ( keys %$br ) {
- if ( exists $pp->{$mod} ) {
- $pp->{$mod} = $br->{$mod} if $br->{$mod} > $pp->{$mod};
- }
- else {
- $pp->{$mod} = $br->{$mod};
- }
- }
+
+unless ( eval { ExtUtils::MakeMaker->VERSION(6.63_03) } ) {
+ delete $WriteMakefileArgs{TEST_REQUIRES};
+ delete $WriteMakefileArgs{BUILD_REQUIRES};
+ $WriteMakefileArgs{PREREQ_PM} = \%FallbackPrereqs;
}
delete $WriteMakefileArgs{CONFIGURE_REQUIRES}
@@ -1,13 +1,15 @@
This archive contains the distribution DBIx-Class-Migration,
-version 0.044:
+version 0.046:
Tools to make migrating your DBIx::Class databases easier
-This software is copyright (c) 2013 by John Napiorkowski.
+This software is copyright (c) 2015 by John Napiorkowski.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
+This README file was generated by Dist::Zilla::Plugin::Readme v5.031.
+
@@ -46,43 +46,43 @@ Utility Commands:
# DESCRIPTION
-[DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler) is a state of the art solution to the problem
-of creating sane workflows for versioning [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) managed database
+[DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler) is a state of the art solution to the problem
+of creating sane workflows for versioning [DBIx::Class](https://metacpan.org/pod/DBIx::Class) managed database
projects. However, since it is more of a toolkit for building custom versioning
and migration workflows than an expression of a particular migration practice,
it might not always be the most approachable tool. If you are starting a new
-[DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) project and you don't have a particular custom workflow need,
+[DBIx::Class](https://metacpan.org/pod/DBIx::Class) project and you don't have a particular custom workflow need,
you might prefer to simply be given a reasonable clear and standard practice,
rather than a toolkit with a set of example scripts.
-[DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration) defines some logic which combines both
-[DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler) and [DBIx::Class::Fixtures](http://search.cpan.org/perldoc?DBIx::Class::Fixtures), along with
+[DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration) defines some logic which combines both
+[DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler) and [DBIx::Class::Fixtures](https://metacpan.org/pod/DBIx::Class::Fixtures), along with
a standard tutorial, to give you a simple and straightforward approach to
solving the problem of how to best create database versions, migrations and
-testing data. Additionally it builds on tools like [Test::mysqld](http://search.cpan.org/perldoc?Test::mysqld) and
-[Test::postgresql](http://search.cpan.org/perldoc?Test::postgresql) along with [DBD::Sqlite](http://search.cpan.org/perldoc?DBD::Sqlite) in order to assist you in quickly
+testing data. Additionally it builds on tools like [Test::mysqld](https://metacpan.org/pod/Test::mysqld) and
+[Test::postgresql](https://metacpan.org/pod/Test::postgresql) along with [DBD::Sqlite](https://metacpan.org/pod/DBD::Sqlite) in order to assist you in quickly
creating a local development database sandbox. It offers some integration
-points to testing your database, via tools like [Test::DBIx::Class](http://search.cpan.org/perldoc?Test::DBIx::Class) in order to
+points to testing your database, via tools like [Test::DBIx::Class](https://metacpan.org/pod/Test::DBIx::Class) in order to
make testing your database driven logic less painful. Lastly, we offer some
thoughts on good development patterns in using databases with application
-frameworks like [Catalyst](http://search.cpan.org/perldoc?Catalyst).
+frameworks like [Catalyst](https://metacpan.org/pod/Catalyst).
-[DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration) offers code and advice based on my experience of using
-[DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) for several years, which hopefully can help you bootstrap a new
-project. The solutions given should work for you if you want to use [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class)
+[DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration) offers code and advice based on my experience of using
+[DBIx::Class](https://metacpan.org/pod/DBIx::Class) for several years, which hopefully can help you bootstrap a new
+project. The solutions given should work for you if you want to use [DBIx::Class](https://metacpan.org/pod/DBIx::Class)
and have database migrations, but don't really know what to do next. These
solutions should scale upward from a small project to a medium project involving
many developers and more than one target environment (DEV -> QA -> Production.)
If you have very complex database versioning requirements, huge teams and
difficult architectual issues, you might be better off building something on
-top of [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler) directly.
+top of [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler) directly.
-[DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration) is a base class upon which interfaces like
-[DBIx::Class::Migration::Script](http://search.cpan.org/perldoc?DBIx::Class::Migration::Script) are built.
+[DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration) is a base class upon which interfaces like
+[DBIx::Class::Migration::Script](https://metacpan.org/pod/DBIx::Class::Migration::Script) are built.
-Please see [DBIx::Class::Migration::Tutorial](http://search.cpan.org/perldoc?DBIx::Class::Migration::Tutorial) for more approachable
+Please see [DBIx::Class::Migration::Tutorial](https://metacpan.org/pod/DBIx::Class::Migration::Tutorial) for more approachable
documentation. If you want to read a high level feature overview, see
-[DBIx::Class::Migration::Features](http://search.cpan.org/perldoc?DBIx::Class::Migration::Features). The remainder of this POD is API level
+[DBIx::Class::Migration::Features](https://metacpan.org/pod/DBIx::Class::Migration::Features). The remainder of this POD is API level
documentation on the various internals.
# ATTRIBUTES
@@ -94,10 +94,10 @@ This class defines the following attributes.
Accept Str. Defaults to 'DBIx::Class::Migration::TargetDirSandboxBuilder'
The name of the helper class which builds the class that builds database
-sandboxs. By default we build database sandboxes in the ["target\_dir"](#target\_dir), which
-is what [DBIx::Class::Migration::TargetDirSandboxBuilder](http://search.cpan.org/perldoc?DBIx::Class::Migration::TargetDirSandboxBuilder) does. We can also
+sandboxs. By default we build database sandboxes in the ["target\_dir"](#target_dir), which
+is what [DBIx::Class::Migration::TargetDirSandboxBuilder](https://metacpan.org/pod/DBIx::Class::Migration::TargetDirSandboxBuilder) does. We can also
build database sandboxes in a temporary directory using
-[DBIx::Class::Migration::TempDirSandboxBuilder](http://search.cpan.org/perldoc?DBIx::Class::Migration::TempDirSandboxBuilder). You might prefer that for
+[DBIx::Class::Migration::TempDirSandboxBuilder](https://metacpan.org/pod/DBIx::Class::Migration::TempDirSandboxBuilder). You might prefer that for
running tests, for example.
## db\_sandbox\_class
@@ -112,19 +112,19 @@ yourself.
This must point to a class that expects `target_dir` and `schema_class` for
initialization arguments and must define a method `make_sandbox` that returns
-an array which can be sent to ["connect" in DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema#connect).
+an array which can be sent to ["connect" in DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema#connect).
-This defaults to [DBIx::Class::Migration::SqliteSandbox](http://search.cpan.org/perldoc?DBIx::Class::Migration::SqliteSandbox). Currently we have
-support for MySQL and Postgresql via [DBIx::Class::Migration::MySQLSandbox](http://search.cpan.org/perldoc?DBIx::Class::Migration::MySQLSandbox)
-and [DBIx::Class::Migration::PgSandbox](http://search.cpan.org/perldoc?DBIx::Class::Migration::PgSandbox), but you will need to side install
-[Test::mysqld](http://search.cpan.org/perldoc?Test::mysqld) and [Test::postgresql](http://search.cpan.org/perldoc?Test::postgresql) (In other words you'd need to add
+This defaults to [DBIx::Class::Migration::SqliteSandbox](https://metacpan.org/pod/DBIx::Class::Migration::SqliteSandbox). Currently we have
+support for MySQL and Postgresql via [DBIx::Class::Migration::MySQLSandbox](https://metacpan.org/pod/DBIx::Class::Migration::MySQLSandbox)
+and [DBIx::Class::Migration::PgSandbox](https://metacpan.org/pod/DBIx::Class::Migration::PgSandbox), but you will need to side install
+[Test::mysqld](https://metacpan.org/pod/Test::mysqld) and [Test::postgresql](https://metacpan.org/pod/Test::postgresql) (In other words you'd need to add
these `Test::*` namespace modules to your `Makefile.PL` or `dist.ini`).
## db\_sandbox
Accepts: Object. Not required.
-This is an instantiated object as defined by ["db\_sandbox\_class"](#db\_sandbox\_class). It is a
+This is an instantiated object as defined by ["db\_sandbox\_class"](#db_sandbox_class). It is a
delegate for the work of automatically creating a local database sandbox that
is useful for developers and for quickly bootstrapping a project.
@@ -134,43 +134,43 @@ Accepts Str. Not Required (but if missing, you need to populate ["schema"](#sch
This is the schema we use as the basis for creating, managing and running your
deployments. This should be the full package namespace defining your subclass
-of [DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema). For example `MyApp::Schema`.
+of [DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema). For example `MyApp::Schema`.
-If the ["schema\_class"](#schema\_class) cannot be loaded, a hard exception will be thrown.
+If the ["schema\_class"](#schema_class) cannot be loaded, a hard exception will be thrown.
## schema\_args
Accepts ArrayRef. Required but lazily builds from defaults
-Provides arguments passed to `connect` on your ["schema\_class"](#schema\_class). Should
+Provides arguments passed to `connect` on your ["schema\_class"](#schema_class). Should
connect to a database.
-This is an arrayref that would work the same as ["connect" in DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema#connect).
-If you choose to create an instance of [DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration) by providing a
-[schema\_class](http://search.cpan.org/perldoc?schema\_class), you can use this to customize how we connect to a database.
+This is an arrayref that would work the same as ["connect" in DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema#connect).
+If you choose to create an instance of [DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration) by providing a
+[schema\_class](https://metacpan.org/pod/schema_class), you can use this to customize how we connect to a database.
If you don't provide a value, we will automatically create a SQLite based
database connection with the following DSN:
DBD:SQLite:[path to target_dir]/[db_file_name].db
-Where c<\[path to target\_dir\]> is ["target\_dir"](#target\_dir) and \[db\_file\_name\] is a converted
-version of ["schema\_class"](#schema\_class). For example if you set [schema\_class](http://search.cpan.org/perldoc?schema\_class) to:
+Where c<\[path to target\_dir\]> is ["target\_dir"](#target_dir) and \[db\_file\_name\] is a converted
+version of ["schema\_class"](#schema_class). For example if you set [schema\_class](https://metacpan.org/pod/schema_class) to:
MyApp::Schema
Then \[db\_file\_name\] would be `myapp-schema`.
Basically, this means you can start testing your database designs right off
-without a lot of effort, just point at a [schema\_class](http://search.cpan.org/perldoc?schema\_class) and get deploying!
+without a lot of effort, just point at a [schema\_class](https://metacpan.org/pod/schema_class) and get deploying!
## schema
-Accepts: Object of [DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema). Not required.
+Accepts: Object of [DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema). Not required.
-If you already have a connected schema (subclass of [DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema))
-you can simple point to it, skipping [schema\_class](http://search.cpan.org/perldoc?schema\_class) and [schema\_args](http://search.cpan.org/perldoc?schema\_args). You
-might for example be using [Catalyst](http://search.cpan.org/perldoc?Catalyst) and want to build deployments for a
+If you already have a connected schema (subclass of [DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema))
+you can simple point to it, skipping [schema\_class](https://metacpan.org/pod/schema_class) and [schema\_args](https://metacpan.org/pod/schema_args). You
+might for example be using [Catalyst](https://metacpan.org/pod/Catalyst) and want to build deployments for a
database that is listed in configuration:
use MyCatalyst::App;
@@ -184,13 +184,13 @@ database that is listed in configuration:
## target\_dir\_builder\_class
Accepts: Str, Defaults to 'DBIx::Class::Migration::ShareDirBuilder'
-This is a class that is used as a helper to build ["target\_dir"](#target\_dir) should the
-user not provide a value. Default is [DBIx::Class::Migration::ShareDirBuilder](http://search.cpan.org/perldoc?DBIx::Class::Migration::ShareDirBuilder)
+This is a class that is used as a helper to build ["target\_dir"](#target_dir) should the
+user not provide a value. Default is [DBIx::Class::Migration::ShareDirBuilder](https://metacpan.org/pod/DBIx::Class::Migration::ShareDirBuilder)
## target\_dir\_builder
-An instance of whatever is in ["target\_dir\_builder\_class"](#target\_dir\_builder\_class). Used by the lazy
-build method of ["target\_dir"](#target\_dir) to default a directory where the migrations are
+An instance of whatever is in ["target\_dir\_builder\_class"](#target_dir_builder_class). Used by the lazy
+build method of ["target\_dir"](#target_dir) to default a directory where the migrations are
actually placed.
## target\_dir
@@ -201,32 +201,32 @@ This is the directory we store our migration and fixture files. Inside this
directory we will create a `fixtures` and `migrations` sub-directory.
Although you can specify the directory, if you leave it undefined, we will use
-[File::ShareDir::ProjectDistDir](http://search.cpan.org/perldoc?File::ShareDir::ProjectDistDir) to locate the `/share` directory for your
+[File::ShareDir::ProjectDistDir](https://metacpan.org/pod/File::ShareDir::ProjectDistDir) to locate the `/share` directory for your
project and place the files there. This is the recommended approach, and is
considered a community practice in regards to where to store your distribution
-non code files. Please see [File::ShareDir::ProjectDistDir](http://search.cpan.org/perldoc?File::ShareDir::ProjectDistDir) as well as
-[File::ShareDir](http://search.cpan.org/perldoc?File::ShareDir) for more information.
+non code files. Please see [File::ShareDir::ProjectDistDir](https://metacpan.org/pod/File::ShareDir::ProjectDistDir) as well as
+[File::ShareDir](https://metacpan.org/pod/File::ShareDir) for more information.
-This uses whatever is in ["schema\_class"](#schema\_class) to determine your project (and look
+This uses whatever is in ["schema\_class"](#schema_class) to determine your project (and look
for a `share` directory, which you'll need to create in your project root).
-If you don't have a ["schema\_class"](#schema\_class) defined, you must have a ["schema"](#schema),
+If you don't have a ["schema\_class"](#schema_class) defined, you must have a ["schema"](#schema),
and we'll infer the class via `ref($self->schema)`.
-__NOTE:__ You'll need to make the `/share` directory if you are going to use
+**NOTE:** You'll need to make the `/share` directory if you are going to use
the default option. We don't automatically create it for you.
## schema\_loader\_class
Accepts Str. Required
-Because your application subclass of [DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema) is going to
+Because your application subclass of [DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema) is going to
change a lot, sometimes we need to generate our own schema and get one that is
in a known, good state. Mostly this is used by the commands to drop tables
and clear tables.
-Defaults to [DBIx::Class::Migration::SchemaLoader](http://search.cpan.org/perldoc?DBIx::Class::Migration::SchemaLoader). You'll probably only
+Defaults to [DBIx::Class::Migration::SchemaLoader](https://metacpan.org/pod/DBIx::Class::Migration::SchemaLoader). You'll probably only
need to change this if your database is crazy and you need to massage the
-init arguments to [DBIx::Class::Schema::Loader](http://search.cpan.org/perldoc?DBIx::Class::Schema::Loader).
+init arguments to [DBIx::Class::Schema::Loader](https://metacpan.org/pod/DBIx::Class::Schema::Loader).
## schema\_loader
@@ -240,11 +240,11 @@ manually.
Accepts Str. Required
-This is the class we use when creating instances of [DBIx::Class::Fixtures](http://search.cpan.org/perldoc?DBIx::Class::Fixtures).
+This is the class we use when creating instances of [DBIx::Class::Fixtures](https://metacpan.org/pod/DBIx::Class::Fixtures).
You'll probably need to review the docs for that and understand how configuration
rules work in order to best take advantage of the system.
-Defaults to [DBIx::Class::Fixtures](http://search.cpan.org/perldoc?DBIx::Class::Fixtures). You'll probably not need to change this
+Defaults to [DBIx::Class::Fixtures](https://metacpan.org/pod/DBIx::Class::Fixtures). You'll probably not need to change this
unless you have some unusual needs regarding fixtures.
## dbic\_fixtures\_extra\_args
@@ -252,18 +252,18 @@ unless you have some unusual needs regarding fixtures.
Accepts HashRef. Required, but Defaults to Empty Hashref
Allows you to pass some additional arguments when creating instances of
-["dbic\_fixture\_class"](#dbic\_fixture\_class). These arguments can be used to override the default
+["dbic\_fixture\_class"](#dbic_fixture_class). These arguments can be used to override the default
initial arguments.
## deployment\_handler\_class
Accepts Str. Required
-This is the class we use when creating instances of [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler).
+This is the class we use when creating instances of [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler).
It would be ideal that you review those docs in order to better understand the
overall architecture of the system.
-Defaults to [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler). You'll probably not need to
+Defaults to [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler). You'll probably not need to
change this unless you need a custom deployment handler, and if you do, I
can't be sure this framework will work correctly, particularly if you are not
useing monotonic versioning.
@@ -272,36 +272,36 @@ useing monotonic versioning.
Accepts HashRef. Required and defaults to an empty hashref.
-Used to pass custom args when building a [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler).
+Used to pass custom args when building a [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler).
Please see the docs for that class for more. Useful args might be `databases`,
`to_version` and `force_overwrite`.
## dbic\_dh
-Accepts Instance of [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler). Required but lazily
-built from default data and [dbic\_dh\_args](http://search.cpan.org/perldoc?dbic\_dh\_args).
+Accepts Instance of [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler). Required but lazily
+built from default data and [dbic\_dh\_args](https://metacpan.org/pod/dbic_dh_args).
You probably won't need to build your own deployment handler and pass it in
-(unlike [schema](http://search.cpan.org/perldoc?schema), where it might actually be useful). Be careful it you do
+(unlike [schema](https://metacpan.org/pod/schema), where it might actually be useful). Be careful it you do
since this framework makes some assumptions about your deployment handler (for
example we assume you are using the monotonic versioning).
-When this attribute is lazily built, we merge ["dbic\_dh\_args"](#dbic\_dh\_args) with the
+When this attribute is lazily built, we merge ["dbic\_dh\_args"](#dbic_dh_args) with the
following defaults:
schema => Points to $self->schema
script_directory => Points to catdir($self->target_dir, 'migrations')
databases => Inferred from your connected schema, defaults to SQLite
-["dbic\_dh\_args"](#dbic\_dh\_args) will overwrite the defaults, if you pass them.
+["dbic\_dh\_args"](#dbic_dh_args) will overwrite the defaults, if you pass them.
## extra\_schemaloader\_args
Optional. Accepts a HashRef of arguments you can use to influence how
-[DBIx::Class::Schema::Loader](http://search.cpan.org/perldoc?DBIx::Class::Schema::Loader) works. This HashRef would get passed as
-`loader_options` (see ["make\_schema\_at" in DBIx::Class::Schema::Loader](http://search.cpan.org/perldoc?DBIx::Class::Schema::Loader#make\_schema\_at).
+[DBIx::Class::Schema::Loader](https://metacpan.org/pod/DBIx::Class::Schema::Loader) works. This HashRef would get passed as
+`loader_options` (see ["make\_schema\_at" in DBIx::Class::Schema::Loader](https://metacpan.org/pod/DBIx::Class::Schema::Loader#make_schema_at).
-Meaningful options are described at [DBIx::Class::Schema::Loader::Base](http://search.cpan.org/perldoc?DBIx::Class::Schema::Loader::Base).
+Meaningful options are described at [DBIx::Class::Schema::Loader::Base](https://metacpan.org/pod/DBIx::Class::Schema::Loader::Base).
# METHODS
@@ -309,7 +309,7 @@ This class defines the following methods for public use
## new
-Used to create an new instance of [DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration). There's a couple
+Used to create an new instance of [DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration). There's a couple
of paths to creating this instance.
### Specify a schema\_class and optionally schema\_args
@@ -321,16 +321,16 @@ of paths to creating this instance.
);
This is probably the most general approach, and is recommended unless you
-already have a connected instance of your [DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema) subclass.
+already have a connected instance of your [DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema) subclass.
-["schema\_args"](#schema\_args) would be anything you'd pass to ["connect" in DBIx::Class::Schema](http://search.cpan.org/perldoc?DBIx::Class::Schema#connect).
-see ["schema\_args"](#schema\_args) for how we construct default connect information if you
+["schema\_args"](#schema_args) would be anything you'd pass to ["connect" in DBIx::Class::Schema](https://metacpan.org/pod/DBIx::Class::Schema#connect).
+see ["schema\_args"](#schema_args) for how we construct default connect information if you
choose to leave this undefined.
### Specify a schema
There may be some cases when you already have a schema object constructed and
-would prefer to just use that. For example, you may be using [Catalyst](http://search.cpan.org/perldoc?Catalyst) and
+would prefer to just use that. For example, you may be using [Catalyst](https://metacpan.org/pod/Catalyst) and
wish to build custom scripts using the built-in dependency and service lookup:
use MyCatalyst::App;
@@ -364,11 +364,11 @@ an alternative location.
### OPTIONAL: Specify dbic\_dh\_args
Optionally, you can specify additional arguments to the constructor for the
-["dbic\_dh"](#dbic\_dh) attribute. Useful arguments might include additional `databases`
+["dbic\_dh"](#dbic_dh) attribute. Useful arguments might include additional `databases`
we should build fixtures for, `to_version` and `force_overwrite`.
-See [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler) for more information on supported init
-arguments. See ["dbic\_dh"](#dbic\_dh) for how we merge default arguments with your custom
+See ["" in DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler) for more information on supported init
+arguments. See ["dbic\_dh"](#dbic_dh) for how we merge default arguments with your custom
arguments.
### Other Initial Arguments
@@ -388,12 +388,12 @@ of the current `schema` version. Sends this as a string to STDOUT
## prepare
-Creates a `fixtures` and `migrations` directory under ["target\_dir"](#target\_dir) (if they
+Creates a `fixtures` and `migrations` directory under ["target\_dir"](#target_dir) (if they
don't already exist) and makes deployment files for the current schema. If
-deployment files exist, will fail unless you ["overwrite\_migrations"](#overwrite\_migrations).
+deployment files exist, will fail unless you ["overwrite\_migrations"](#overwrite_migrations).
The `migrations` directory reflects a directory structure as documented in
-[DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler).
+[DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler).
If this is the first version, we create directories and initial DLL, etc. For
versions greater than 1, we will also generate diffs and copy any fixture
@@ -403,11 +403,11 @@ safety reasons, we never overwrite any fixture configs.
## install
Installs either the current schema version (if already prepared) or the target
-version specified via any `to_version` flags sent as an [dbic\_dh\_args](http://search.cpan.org/perldoc?dbic\_dh\_args) to the
+version specified via any `to_version` flags sent as an [dbic\_dh\_args](https://metacpan.org/pod/dbic_dh_args) to the
database which is connected via ["schema"](#schema).
If you try to install to a database that has already been installed, you'll get
-an error. See ["drop\_tables"](#drop\_tables).
+an error. See ["drop\_tables"](#drop_tables).
## upgrade
@@ -443,8 +443,8 @@ version.
## make\_schema
-Given an existing database, reverse engineer a [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) Schema in the
-["target\_dir"](#target\_dir) (under `dumped_db`). You can use this if you need to bootstrap
+Given an existing database, reverse engineer a [DBIx::Class](https://metacpan.org/pod/DBIx::Class) Schema in the
+["target\_dir"](#target_dir) (under `dumped_db`). You can use this if you need to bootstrap
your DBIC files.
## populate
@@ -453,23 +453,23 @@ Given an array of fixture set names, populate the current database version with
the matching sets for that version.
Skips the table `dbix_class_deploymenthandler_versions`, so you don't lose
-deployment info (this is different from ["drop\_tables"](#drop\_tables) which does delete it.)
+deployment info (this is different from ["drop\_tables"](#drop_tables) which does delete it.)
## diagram
Experimental feature. Although not specifically a migration task, I find it
useful to output visuals of my databases. This command will place a file in
-your ["target\_dir"](#target\_dir) called `db-diagram-vXXX.png` where `XXX` is he current
+your ["target\_dir"](#target_dir) called `db-diagram-vXXX.png` where `XXX` is he current
`schema` version.
-This is using the Graphviz producer ([SQL::Translator::Producer::GraphViz](http://search.cpan.org/perldoc?SQL::Translator::Producer::GraphViz))
-which in turn requires [Graphviz](http://search.cpan.org/perldoc?Graphviz). Since this is not always trivial to
+This is using the Graphviz producer ([SQL::Translator::Producer::GraphViz](https://metacpan.org/pod/SQL::Translator::Producer::GraphViz))
+which in turn requires [Graphviz](https://metacpan.org/pod/Graphviz). Since this is not always trivial to
install, I do not require it. You will need to add it manually to your
`Makefile.PL` or `dist.ini` and manage it yourself.
This feature is experimental and currently does not offer any options, as I
am still determining the best way to meet the need without exceeding the
-scope of [DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration). Consider this command a 'freebee' and
+scope of [DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration). Consider this command a 'freebee' and
please don't depend on it in your custom code.
## install\_if\_needed
@@ -524,9 +524,9 @@ control repository).
# ENVIRONMENT
-When running [DBIx::Class::Migration](http://search.cpan.org/perldoc?DBIx::Class::Migration) we set some `%ENV` variables during
+When running [DBIx::Class::Migration](https://metacpan.org/pod/DBIx::Class::Migration) we set some `%ENV` variables during
installation, up / downgrading, so that your Perl run scripts (see
-["DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator\\'PERL SCRIPTS'"](#DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator\\'PERL SCRIPTS'))
+["DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator\\'PERL SCRIPTS'"](#dbix-class-deploymenthandler-deploymethod-sql-translator-perl-scripts))
can receive some useful information. The Following `%ENV` variables are set:
DBIC_MIGRATION_SCHEMA_CLASS => $self->schema_class
@@ -550,18 +550,18 @@ particular projects / people I'd like to thank:
First, thanks to `mst` for providing me a big chunk of code that served to
kickstart my work, and served as an valuable prototype.
-Thanks to `frew` for the awesome [DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler) which gives
+Thanks to `frew` for the awesome [DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler) which gives
us such a powerful base for organizing database versions. Thanks to all the
-authors of [DBIx::Class::Fixtures](http://search.cpan.org/perldoc?DBIx::Class::Fixtures) for giving me a foundation for managing
-sets of data. Lastly, thanks to the [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) cabal for all the work done
-in making the [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class) ORM so amazingly powerful.
+authors of [DBIx::Class::Fixtures](https://metacpan.org/pod/DBIx::Class::Fixtures) for giving me a foundation for managing
+sets of data. Lastly, thanks to the [DBIx::Class](https://metacpan.org/pod/DBIx::Class) cabal for all the work done
+in making the [DBIx::Class](https://metacpan.org/pod/DBIx::Class) ORM so amazingly powerful.
-Additionally thanks to the creators / maintainers for [Test::mysqld](http://search.cpan.org/perldoc?Test::mysqld) and
-[Test::postgresql](http://search.cpan.org/perldoc?Test::postgresql), which made it easy to create developer level sandboxes for
+Additionally thanks to the creators / maintainers for [Test::mysqld](https://metacpan.org/pod/Test::mysqld) and
+[Test::postgresql](https://metacpan.org/pod/Test::postgresql), which made it easy to create developer level sandboxes for
these popular open source databases.
-As usual, thanks to the [Moose](http://search.cpan.org/perldoc?Moose) cabal for making Perl programming fun and
-beautiful. Lastly, a shout-out to the [Dist::Zilla](http://search.cpan.org/perldoc?Dist::Zilla) cabal for making it so I
+As usual, thanks to the [Moose](https://metacpan.org/pod/Moose) cabal for making Perl programming fun and
+beautiful. Lastly, a shout-out to the [Dist::Zilla](https://metacpan.org/pod/Dist::Zilla) cabal for making it so I
don't need to write my own build and deployment tools.
# AUTHOR
@@ -587,10 +587,10 @@ missed you.
# SEE ALSO
-[DBIx::Class::DeploymentHandler](http://search.cpan.org/perldoc?DBIx::Class::DeploymentHandler), [DBIx::Class::Fixtures](http://search.cpan.org/perldoc?DBIx::Class::Fixtures), [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class),
-[DBIx::Class::Schema::Loader](http://search.cpan.org/perldoc?DBIx::Class::Schema::Loader), [Moose](http://search.cpan.org/perldoc?Moose), [DBIx::Class::Migration::Script](http://search.cpan.org/perldoc?DBIx::Class::Migration::Script),
-[DBIx::Class::Migration::Population](http://search.cpan.org/perldoc?DBIx::Class::Migration::Population), [dbic-migration](http://search.cpan.org/perldoc?dbic-migration), [SQL::Translator](http://search.cpan.org/perldoc?SQL::Translator),
-[Test::mysqld](http://search.cpan.org/perldoc?Test::mysqld), [Test::postgresql](http://search.cpan.org/perldoc?Test::postgresql).
+[DBIx::Class::DeploymentHandler](https://metacpan.org/pod/DBIx::Class::DeploymentHandler), [DBIx::Class::Fixtures](https://metacpan.org/pod/DBIx::Class::Fixtures), [DBIx::Class](https://metacpan.org/pod/DBIx::Class),
+[DBIx::Class::Schema::Loader](https://metacpan.org/pod/DBIx::Class::Schema::Loader), [Moose](https://metacpan.org/pod/Moose), [DBIx::Class::Migration::Script](https://metacpan.org/pod/DBIx::Class::Migration::Script),
+[DBIx::Class::Migration::Population](https://metacpan.org/pod/DBIx::Class::Migration::Population), [dbic-migration](https://metacpan.org/pod/dbic-migration), [SQL::Translator](https://metacpan.org/pod/SQL::Translator),
+[Test::mysqld](https://metacpan.org/pod/Test::mysqld), [Test::postgresql](https://metacpan.org/pod/Test::postgresql).
# COPYRIGHT & LICENSE
@@ -2,10 +2,16 @@ name = DBIx-Class-Migration
author = John Napiorkowski <jjnapiork@cpan.org>
license = Perl_5
copyright_holder = John Napiorkowski
-copyright_year = 2013
+copyright_year = 2015
abstract = Tools to make migrating your DBIx::Class databases easier
-version = 0.044
+main_module = lib/DBIx/Class/Migration.pm
+[NextRelease]
+[Git::Tag]
+[VersionFromModule]
+[Git::Contributors]
+
+[Git::Push]
[@ConfigSlicer]
-bundle = @Basic
GatherDir.include_dotfiles = 1
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/.DS_Store
deleted file mode 100644
index e950b39d..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/.DS_Store
deleted file mode 100644
index 07ae8b67..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/.DS_Store
deleted file mode 100644
index 6989c24b..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.DS_Store
deleted file mode 100644
index 7fbb826c..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.FAQ.pod.swp b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.FAQ.pod.swp
deleted file mode 100644
index 75afec91..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/.FAQ.pod.swp and /dev/null differ
@@ -1,7 +1,7 @@
package DBIx::Class::Migration::PostgresqlSandbox;
use Moose;
-use Test::postgresql;
+use Test::PostgreSQL;
use File::Spec::Functions 'catdir', 'catfile';
use File::Path 'mkpath';
use POSIX qw(SIGINT);
@@ -35,8 +35,8 @@ sub _build_test_postgresql {
my %config = (
auto_start => $auto_start,
base_dir => $base_dir,
- initdb_args => $Test::postgresql::Defaults{initdb_args},
- postmaster_args => $Test::postgresql::Defaults{postmaster_args});
+ initdb_args => $Test::PostgreSQL::Defaults{initdb_args},
+ postmaster_args => $Test::PostgreSQL::Defaults{postmaster_args});
unless($auto_start) {
open ( my $pid_fh, '<', catdir($base_dir, 'data','postmaster.pid')) ||
@@ -46,10 +46,10 @@ sub _build_test_postgresql {
$config{port} = $lines[3];
}
- if(my $testdb = Test::postgresql->new(%config)) {
+ if(my $testdb = Test::PostgreSQL->new(%config)) {
return $testdb;
} else {
- die $Test::postgresql::errstr;
+ die $Test::PostgreSQL::errstr;
}
}
@@ -160,7 +160,7 @@ DBIx::Class::Migration::PostgresqlSandbox - Autocreate a postgresql sandbox
This automatically creates a postgresql sandbox in your C<target_dir> that you can
use for initial prototyping, development and demonstration. If you want to
-use this, you will need to add L<Test::postgresql> to your C<Makefile.PL> or your
+use this, you will need to add L<Test::PostgreSQL> to your C<Makefile.PL> or your
C<dist.ini> file, and get that installed properly. It also requires that you
have Postgresql installed locally (although Postgresql does not need to be running, as
long as we can find in $PATH the binary installation). If your copy of Postgresql
@@ -211,7 +211,7 @@ queries).
=head1 SEE ALSO
-L<DBIx::Class::Migration>, L<DBD::Pg>, L<Test::postgresql>.
+L<DBIx::Class::Migration>, L<DBD::Pg>, L<Test::PostgreSQL>.
=head1 AUTHOR
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/Script/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/Script/.DS_Store
deleted file mode 100644
index 6abe9005..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/lib/DBIx/Class/Migration/Script/.DS_Store and /dev/null differ
@@ -17,7 +17,7 @@ Reviewing the documentation for L<Catalyst::Test> would be valuable, as well as
L<Catalyst::Plugin::ConfigLoader> for a refresher on the idea of localized and
enviroment specific configurations.
-=head1 Bootrap a basic Catalyst application
+=head1 Bootstrap a basic Catalyst application
Update you C<dist.ini> file:
@@ -71,6 +71,11 @@ manually:
mkdir share/html
touch share/html/index.tt
+If you prefer to use a helper, you can also try
+L<https://metacpan.org/pod/Dist::Zilla::Plugin::Catalyst::New> it generates
+part of the files L<catalyst.pl> creates but is closer to the normal
+Dist::Zilla stuff.
+
Now open C<lib/MusicBase/Web.pm> and change it to look like this:
package MusicBase::Web;
@@ -1,11 +1,12 @@
package DBIx::Class::Migration;
-our $VERSION = "0.044";
+our $VERSION = "0.046";
+$VERSION = eval $VERSION;
use Moose;
use JSON::XS;
use File::Copy 'cp';
-use File::Spec::Functions 'catdir', 'catfile';
+use File::Spec::Functions 'catdir', 'catfile', 'updir';
use File::Path 'mkpath', 'remove_tree';
use DBIx::Class::Migration::Types 'LoadableClass', 'LoadableDBICSchemaClass';
use Class::Load 'load_class';
@@ -397,7 +398,7 @@ sub dump_named_sets {
directory_template => sub {
my ($fixture, $params, $set) = @_;
$set =~s/\.json//;
- my $fixture_conf_dir = $fixture->config_dir->parent->subdir($set);
+ my $fixture_conf_dir = catfile($fixture->config_dir,updir,$set);
mkpath($fixture_conf_dir)
unless -d $fixture_conf_dir;
return $fixture_conf_dir;
@@ -416,7 +417,7 @@ sub dump_all_sets {
directory_template => sub {
my ($fixture, $params, $set) = @_;
$set =~s/\.json//;
- my $fixture_conf_dir = $fixture->config_dir->parent->subdir($set);
+ my $fixture_conf_dir = catfile($fixture->config_dir,updir,$set);
mkpath($fixture_conf_dir)
unless -d $fixture_conf_dir;
return $fixture_conf_dir;
@@ -427,7 +428,7 @@ sub dump_all_sets {
sub delete_named_sets {
my ($self, @sets) = @_;
my $fixtures = $self->build_dbic_fixtures;
- my @paths = map { $fixtures->config_dir->parent->subdir($_) } @sets;
+ my @paths = map { catfile($fixtures->config_dir,updir,$_) } @sets;
foreach my $path (@paths) {
$self->_delete_path($path);
}
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/.DS_Store
deleted file mode 100644
index c016a872..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/.DS_Store
deleted file mode 100644
index 60c200f0..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/.DS_Store
deleted file mode 100644
index bc2fe7fc..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/Schema/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/Schema/.DS_Store
deleted file mode 100644
index 41b6430e..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/Schema/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/.DS_Store
deleted file mode 100644
index a6b0e690..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/Schema/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/Schema/.DS_Store
deleted file mode 100644
index 45de97b0..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/lib/Local/v2/Schema/.DS_Store and /dev/null differ
diff --git a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/share/.DS_Store b/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/share/.DS_Store
deleted file mode 100644
index 5008ddfc..00000000
Binary files a/var/tmp/source/JJNAPIORK/DBIx-Class-Migration-0.044/DBIx-Class-Migration-0.044/t/share/.DS_Store and /dev/null differ