Major changes related to reports

backend/internal/database/migrations/0030_time_reports.sql

@@ -1,22 +0,0 @@
-CREATE TABLE IF NOT EXISTS time_reports (
-  id INTEGER PRIMARY KEY,
-  project_id INTEGER NOT NULL,
-  user_id INTEGER NOT NULL,
-  activity_type TEXT NOT NULL,
-  start DATETIME NOT NULL,
-  end DATETIME NOT NULL,
-  FOREIGN KEY (project_id) REFERENCES projects (id) ON DELETE CASCADE
-  FOREIGN KEY (user_id) REFERENCES users (id) ON DELETE CASCADE
-  FOREIGN KEY (activity_type) REFERENCES activity_types (name) ON DELETE CASCADE
-);
-
-CREATE TRIGGER IF NOT EXISTS time_reports_start_before_end
-  BEFORE INSERT ON time_reports
-  FOR EACH ROW
-  BEGIN
-    SELECT
-      CASE
-        WHEN NEW.start >= NEW.end THEN
-          RAISE (ABORT, 'start must be before end')
-      END;
-  END;

backend/internal/database/migrations/0035_weekly_report.sql

@@ -0,0 +1,14 @@
+CREATE TABLE weekly_reports (
+  user_id INTEGER,
+  project_id INTEGER,
+  week INTEGER,
+  development_time INTEGER,
+  meeting_time INTEGER,
+  admin_time INTEGER,
+  own_work_time INTEGER,
+  study_time INTEGER,
+  testing_time INTEGER,
+  FOREIGN KEY (user_id) REFERENCES users(id),
+  FOREIGN KEY (project_id) REFERENCES projects(id)
+  PRIMARY KEY (user_id, project_id, week)
+)

backend/internal/database/migrations/0040_time_report_collections.sql

@@ -1,9 +0,0 @@
-CREATE TABLE IF NOT EXISTS report_collection (
-  id INTEGER PRIMARY KEY,
-  owner_id INTEGER NOT NULL,
-  project_id INTEGER NOT NULL,
-  date DATE NOT NULL,
-  signed_by INTEGER, -- NULL if not signed
-  FOREIGN KEY (owner_id) REFERENCES users (id)
-  FOREIGN KEY (signed_by) REFERENCES users (id)
-);

backend/internal/database/migrations/0070_salts.sql

@@ -1,16 +0,0 @@
--- It is unclear weather this table will be used
-
--- Create the table to store hash salts
-CREATE TABLE IF NOT EXISTS salts (
-    id INTEGER PRIMARY KEY,
-    salt TEXT NOT NULL
-);
-
--- Commented out for now, no time for good practices, which is atrocious
--- Create a trigger to automatically generate a salt when inserting a new user record
--- CREATE TRIGGER generate_salt_trigger
--- AFTER INSERT ON users
--- BEGIN
---     INSERT INTO salts (salt) VALUES (randomblob(16));
---     UPDATE users SET salt_id = (SELECT last_insert_rowid()) WHERE id = new.id;
--- END;

backend/internal/database/migrations/0080_activity_types.sql

@@ -1,10 +0,0 @@
-CREATE TABLE IF NOT EXISTS activity_types (
-  name TEXT PRIMARY KEY
-);
-
-INSERT OR IGNORE INTO activity_types (name) VALUES ('Development');
-INSERT OR IGNORE INTO activity_types (name) VALUES ('Meeting');
-INSERT OR IGNORE INTO activity_types (name) VALUES ('Administration');
-INSERT OR IGNORE INTO activity_types (name) VALUES ('Own Work');
-INSERT OR IGNORE INTO activity_types (name) VALUES ('Studies');
-INSErt OR IGNORE INTO activity_types (name) VALUES ('Testing');