From ecb16565531b349acda366515ebb2f9fc1cc24a3 Mon Sep 17 00:00:00 2001 From: Janik Kleinhoff Date: Mon, 13 Feb 2017 21:51:10 +0000 Subject: DB: fix major fuckup "id" in the alertlog table refers to the ID name of the alert rule that triggered, **not** to some sort of unique ID. This commit rewrites the database schema history used by DBIx::Class::DeploymentHandler as the previous schemata were utterly useless (and, in fact, seem to be undeployable). @Unit193, @Xenthys Clearly you managed to deploy a database somehow. If you used the legacy `DATABASE.SCHEMA` file and `bin/db_legacy`, you should be able to update via `bin/db_upgrade`; I've tested to verify this. (If you //haven't// run `db_legacy` yet, make sure to update to exactly de9f3deabe35, run `db_legacy`, then update to this commit and proceed with `db_upgrade`.) If you used the `db_deploy` script, may Cthulhu have mercy on your soul: I'm pretty sure that would not actually have worked. That said, it's my mistake, so if you require further assistance, feel free to poke me on freenode. --- bin/db_legacy | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'bin') diff --git a/bin/db_legacy b/bin/db_legacy index 6f0208c..3206d33 100755 --- a/bin/db_legacy +++ b/bin/db_legacy @@ -24,8 +24,9 @@ my $dh = DBIx::Class::DeploymentHandler->new({ schema => $schema, schema_version => '' . $schema->schema_version, sql_translator_args => { add_drop_table => 0, quote_identifiers => 1 }, + databases => [], + ignore_ddl => 1, }); -$dh->prepare_version_storage_install; $dh->install_version_storage; $dh->add_database_version({ version => 1 }); -- cgit v1.2.3