X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FSchema%2FVersioned.pm;h=6966e5bf37b869a08cfb814315bdf66641dc1747;hb=a28009914a3e447af53737d503b1953160d146c9;hp=ba38ad791ec445f23b6290901d8f6a905119d164;hpb=c9d2e0a20b79cf2c65ff86e8b400ff683b18627d;p=dbsrgits%2FDBIx-Class.git diff --git a/lib/DBIx/Class/Schema/Versioned.pm b/lib/DBIx/Class/Schema/Versioned.pm index ba38ad7..6966e5b 100644 --- a/lib/DBIx/Class/Schema/Versioned.pm +++ b/lib/DBIx/Class/Schema/Versioned.pm @@ -47,14 +47,34 @@ use Data::Dumper; __PACKAGE__->mk_classdata('_filedata'); __PACKAGE__->mk_classdata('upgrade_directory'); +__PACKAGE__->mk_classdata('backup_directory'); -sub on_connect +sub schema_version { + my ($self) = @_; + my $class = ref($self)||$self; + my $version; + { + no strict 'refs'; + $version = ${"${class}::VERSION"}; + } + return $version; +} + +sub connection { + my $self = shift; + $self->next::method(@_); + $self->_on_connect; + return $self; +} + +sub _on_connect { my ($self) = @_; my $vschema = DBIx::Class::Version->connect(@{$self->storage->connect_info()}); my $vtable = $vschema->resultset('Table'); my $pversion; - if(!$self->exists($vtable)) + + if(!$self->_source_exists($vtable)) { # $vschema->storage->debug(1); $vschema->storage->ensure_connected(); @@ -74,7 +94,7 @@ sub on_connect $pversion = $pversion->Version if($pversion); } # warn("Previous version: $pversion\n"); - if($pversion eq $self->VERSION) + if($pversion eq $self->schema_version) { warn "This version is already installed\n"; return 1; @@ -84,7 +104,7 @@ sub on_connect if(!$pversion) { - $vtable->create({ Version => $self->VERSION, + $vtable->create({ Version => $self->schema_version, Installed => strftime("%Y-%m-%d %H:%M:%S", gmtime()) }); ## If we let the user do this, where does the Version table get updated? @@ -96,7 +116,7 @@ sub on_connect my $file = $self->ddl_filename( $self->storage->sqlt_type, $self->upgrade_directory, - $self->VERSION + $self->schema_version ); if(!$file) { @@ -107,10 +127,10 @@ sub on_connect $file = $self->ddl_filename( $self->storage->sqlt_type, $self->upgrade_directory, - $self->VERSION, + $self->schema_version, $pversion, ); -# $file =~ s/@{[ $self->VERSION ]}/"${pversion}-" . $self->VERSION/e; +# $file =~ s/@{[ $self->schema_version ]}/"${pversion}-" . $self->schema_version/e; if(!-f $file) { warn "Upgrade not possible, no upgrade file found ($file)\n"; @@ -128,12 +148,12 @@ sub on_connect ## Don't do this yet, do only on command? ## If we do this later, where does the Version table get updated?? - warn "Versions out of sync. This is " . $self->VERSION . + warn "Versions out of sync. This is " . $self->schema_version . ", your database contains version $pversion, please call upgrade on your Schema.\n"; -# $self->upgrade($pversion, $self->VERSION); +# $self->upgrade($pversion, $self->schema_version); } -sub exists +sub _source_exists { my ($self, $rs) = @_; @@ -149,7 +169,7 @@ sub backup { my ($self) = @_; ## Make each ::DBI::Foo do this - $self->storage->backup(); + $self->storage->backup($self->backup_directory()); } sub upgrade @@ -169,7 +189,7 @@ sub upgrade my $vschema = DBIx::Class::Version->connect(@{$self->storage->connect_info()}); my $vtable = $vschema->resultset('Table'); - $vtable->create({ Version => $self->VERSION, + $vtable->create({ Version => $self->schema_version, Installed => strftime("%Y-%m-%d %H:%M:%S", gmtime()) }); } @@ -193,6 +213,8 @@ sub run_upgrade return 1; } +1; + =head1 NAME DBIx::Class::Versioning - DBIx::Class::Schema plugin for Schema upgrades @@ -206,6 +228,7 @@ DBIx::Class::Versioning - DBIx::Class::Schema plugin for Schema upgrades __PACKAGE__->load_components(qw/+DBIx::Class::Schema::Versioned/); __PACKAGE__->upgrade_directory('/path/to/upgrades/'); + __PACKAGE__->backup_directory('/path/to/backups/'); sub backup { @@ -244,6 +267,11 @@ in L. Return a false value if there is no upgrade path between the two versions supplied. By default, every change in your VERSION is regarded as needing an upgrade. +The actual upgrade is called manually by calling C on your +schema object. Code is run at connect time to determine whether an +upgrade is needed, if so, a warning "Versions out of sync" is +produced. + NB: At the moment, SQLite upgrading is rather spotty, as SQL::Translator::Diff returns SQL statements that SQLite does not support. @@ -280,6 +308,21 @@ idea is that this method can be called any number of times from your C method, running whichever commands you specify via the regex in the parameter. +=head2 upgrade_directory + +Use this to set the directory your upgrade files are stored in. + +=head2 backup_directory + +Use this to set the directory you want your backups stored in. + +=head2 schema_version + +Returns the current schema class' $VERSION; does -not- use $schema->VERSION +since that varies in results depending on if version.pm is installed, and if +so the perl or XS versions. If you want this to change, bug the version.pm +author to make vpp and vxs behave the same. + =head1 AUTHOR Jess Robinson