From 07d757e9afaf9c6f8fba9e53e4737ebf7988faa7 Mon Sep 17 00:00:00 2001 From: Patrick Mueller Date: Thu, 13 Aug 2026 21:02:47 +0200 Subject: [PATCH] Remove hardcoded USE statement from feedback schema migration 001_init.sql opened with USE `nachklang-feedback`, contradicting its own documented apply instructions (mysql ... < 001_init.sql, which already selects the database via the command line). Following the file's own usage note literally would fail unless a database happened to be named exactly nachklang-feedback rather than whatever FEEDBACK_DB is configured to in .env. Co-Authored-By: Claude Sonnet 5 --- sql/feedback/001_init.sql | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/feedback/001_init.sql b/sql/feedback/001_init.sql index 4fd61cc..ebd0c2d 100644 --- a/sql/feedback/001_init.sql +++ b/sql/feedback/001_init.sql @@ -6,8 +6,10 @@ -- -- Apply with e.g.: -- mysql -h -u -p < 001_init.sql - -USE `nachklang-feedback`; +-- +-- Deliberately no USE statement here: the target database is selected via +-- the mysql command line above (whatever FEEDBACK_DB is actually named in +-- .env), not hardcoded to a literal schema name. -- 1. events ------------------------------------------------------------- CREATE TABLE events (