Hi All,
I've been trying out Minion with Minion::Backend::Pg, it works well.
One little thing, though : I'd like the minion-specific tables to be
in their own schema (but in the same database).
I thought maybe this would work :
plugin 'minion' => Pg => 'postgresql:///fresh';
app->minion->backend->pg->db->do(q[set search_path='minion']) or die 'db
error';
app->minion->backend->pg->migrations->migrate;
It almost does, but the first line generates the minion tables
in the 'public' (default) schema before the second line gets a chance
to execute, so I end up with an extra set of tables.
Is there a better way to accompish this?
(I also tried using the Mojo::Pg 'connection' event but couldn't set
the event since the backend constructor makes the Mojo::Pg object itself
and then uses the connection event to do the migration).
thanks
Brian
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
