Skip to content

use TimeStamp for setting the changeset timestamp #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

use TimeStamp for setting the changeset timestamp #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 2 additions & 13 deletions lib/DBIx/Class/Schema/Journal/DB/ChangeSet.pm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ use base 'DBIx::Class::Core';
sub journal_define_table {
my ( $class, $schema_class, $prefix ) = @_;

$class->load_components(qw/InflateColumn::DateTime/);
$class->load_components(qw/InflateColumn::DateTime TimeStamp/);
$class->table($prefix . 'changeset');

$class->add_columns(
Expand All @@ -23,6 +23,7 @@ sub journal_define_table {
set_date => {
data_type => 'timestamp',
is_nullable => 0,
set_on_create => 1,
},
session_id => {
data_type => 'varchar',
Expand All @@ -34,16 +35,4 @@ sub journal_define_table {
$class->set_primary_key('ID');
}

sub new {
my $self = shift->next::method(@_);
# I think we should not do the following and
# instead use DBIx::Class::TimeStamp. If I
# can think of a good way (passing a version on
# import?) to do it and retain backcompat I will.
#
# --fREW, 01-27-2010
$self->set_date(scalar gmtime);
return $self;
}

1;