new table for settings and store blocked date there;

non admins can't enter avs before the blocked date
new table for survey

prisma/migrations/20240614185207_/migration.sql

@@ -0,0 +1,9 @@
+-- CreateTable
+CREATE TABLE `Settings` (
+    `id` INTEGER NOT NULL AUTO_INCREMENT,
+    `key` VARCHAR(191) NOT NULL,
+    `value` VARCHAR(191) NOT NULL,
+    `description` VARCHAR(191) NULL,
+
+    PRIMARY KEY (`id`)
+) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

prisma/migrations/20240614213436_modify_settings_table/migration.sql

@@ -0,0 +1,10 @@
+/*
+Warnings:
+- The primary key for the `settings` table will be changed. If it partially fails, the table could be left without primary key constraint.
+- You are about to drop the column `id` on the `settings` table. All the data in the column will be lost.
+*/
+-- AlterTable
+ALTER TABLE `Settings`
+DROP PRIMARY KEY,
+DROP COLUMN `id`,
+ADD PRIMARY KEY (`key`);

prisma/migrations/20240616203120_add_survey_table/migration.sql

@@ -0,0 +1,19 @@
+-- AlterTable
+ALTER TABLE `message` ADD COLUMN `answer` VARCHAR(191) NULL,
+    ADD COLUMN `answerDate` DATETIME(3) NULL,
+    ADD COLUMN `shownDate` DATETIME(3) NULL,
+    ADD COLUMN `surveyId` INTEGER NULL;
+
+-- CreateTable
+CREATE TABLE `Survey` (
+    `id` INTEGER NOT NULL AUTO_INCREMENT,
+    `content` VARCHAR(191) NOT NULL,
+    `answers` JSON NULL,
+    `publicFrom` DATETIME(3) NULL,
+    `publicUntil` DATETIME(3) NULL,
+
+    PRIMARY KEY (`id`)
+) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
+
+-- AddForeignKey
+ALTER TABLE `Message` ADD CONSTRAINT `Message_surveyId_fkey` FOREIGN KEY (`surveyId`) REFERENCES `Survey`(`id`) ON DELETE SET NULL ON UPDATE CASCADE;