Potential fix for schema deploy issue
This commit is contained in:
parent
4d7adc1cef
commit
69489585bf
|
@ -13,7 +13,9 @@ my $lastexpunge = 0;
|
||||||
|
|
||||||
sub DeploySchema {
|
sub DeploySchema {
|
||||||
# TODO: figure out how to ensure schema is deployed without producing "table already exists" errors when it is already deployed
|
# TODO: figure out how to ensure schema is deployed without producing "table already exists" errors when it is already deployed
|
||||||
|
no warnings;
|
||||||
eval {schema->deploy};
|
eval {schema->deploy};
|
||||||
|
use warnings;
|
||||||
}
|
}
|
||||||
sub DateTimeToQueryable {
|
sub DateTimeToQueryable {
|
||||||
my $dt = DateTime->now(time_zone => config->{tz});
|
my $dt = DateTime->now(time_zone => config->{tz});
|
||||||
|
|
Loading…
Reference in New Issue