You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I overcame it temporarily with the following in my Schema class.. hopefully it helps
use utf8;
packageRebus::Schema;
use strict;
use warnings;
use base 'DBIx::Class::Schema';
our$VERSION = 18;
__PACKAGE__->load_namespaces;
=head1DEPLOY HOOKS=head2rebus triggers=cutsubsqlt_deploy_hook {
my ($self, $sqlt_schema) = @_;
# Hack to prevent hook being called for a second time (as thus fail) with DeploymentHandlerreturnif @{$sqlt_schema->get_tables} == 1 and$sqlt_schema->get_tables->[0]->name eq'dbix_class_deploymenthandler_versions';
...
index's, triggers, whatever here ...}
Is it your expectation that the hook wouldn't get called for installing the database-version RS? We could just local monkey-patch the hook out in that situation, which seems reasonable.
As the title says, the sqlt_deploy-hook can end up getting called twice, once for the versions tables only it seems and once for everything else.
The text was updated successfully, but these errors were encountered: