Initial implementation of db stuffs

Got the migrations and datastructures in. Next step is building db
utility function into the db module or client module

migrations/00000000000000_diesel_initial_setup/down.sql

@@ -0,0 +1,6 @@
+-- This file was automatically created by Diesel to setup helper functions
+-- and other internal bookkeeping. This file is safe to edit, any future
+-- changes will be added to existing projects as new migrations.
+
+DROP FUNCTION IF EXISTS diesel_manage_updated_at(_tbl regclass);
+DROP FUNCTION IF EXISTS diesel_set_updated_at();

migrations/00000000000000_diesel_initial_setup/up.sql

@@ -0,0 +1,36 @@
+-- This file was automatically created by Diesel to setup helper functions
+-- and other internal bookkeeping. This file is safe to edit, any future
+-- changes will be added to existing projects as new migrations.
+
+
+
+
+-- Sets up a trigger for the given table to automatically set a column called
+-- `updated_at` whenever the row is modified (unless `updated_at` was included
+-- in the modified columns)
+--
+-- # Example
+--
+-- ```sql
+-- CREATE TABLE users (id SERIAL PRIMARY KEY, updated_at TIMESTAMP NOT NULL DEFAULT NOW());
+--
+-- SELECT diesel_manage_updated_at('users');
+-- ```
+CREATE OR REPLACE FUNCTION diesel_manage_updated_at(_tbl regclass) RETURNS VOID AS $$
+BEGIN
+    EXECUTE format('CREATE TRIGGER set_updated_at BEFORE UPDATE ON %s
+                    FOR EACH ROW EXECUTE PROCEDURE diesel_set_updated_at()', _tbl);
+END;
+$$ LANGUAGE plpgsql;
+
+CREATE OR REPLACE FUNCTION diesel_set_updated_at() RETURNS trigger AS $$
+BEGIN
+    IF (
+        NEW IS DISTINCT FROM OLD AND
+        NEW.updated_at IS NOT DISTINCT FROM OLD.updated_at
+    ) THEN
+        NEW.updated_at := current_timestamp;
+    END IF;
+    RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;

migrations/2026-05-18-182001-0000_create_users/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE users;

migrations/2026-05-18-182001-0000_create_users/up.sql

@@ -0,0 +1,6 @@
+-- Your SQL goes here
+CREATE TABLE users (
+  id SERIAL PRIMARY KEY,
+  username TEXT NOT NULL UNIQUE,
+  password TEXT NOT NULL
+)

migrations/2026-05-18-182012-0000_create_groups/down.sql

@@ -0,0 +1,3 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE groups;
+DROP TYPE user_t;

migrations/2026-05-18-182012-0000_create_groups/up.sql

@@ -0,0 +1,11 @@
+-- Your SQL goes here
+CREATE TYPE user_t AS (
+    name TEXT,
+    server TEXT
+);
+CREATE TABLE groups (
+  id SERIAL PRIMARY KEY,
+  groupname TEXT NOT NULL,
+  role TEXT,
+  username user_t NOT NULL
+)

migrations/2026-05-18-182028-0000_create_messages/down.sql

@@ -0,0 +1,3 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE messages;
+DROP TYPE room_id;

migrations/2026-05-18-182028-0000_create_messages/up.sql

@@ -0,0 +1,14 @@
+-- Your SQL goes here
+CREATE TYPE room_id AS (
+    coordinates bigint[],
+    server text
+);
+CREATE TABLE messages (
+    id BIGSERIAL PRIMARY KEY,
+    room room_id NOT NULL,
+    body TEXT NOT NULL,
+    signature TEXT NOT NULL,
+    client_timestamp BIGINT NOT NULL,
+    server_timestamp BIGINT NOT NULL,
+    username user_t NOT NULL
+)

migrations/2026-05-18-182143-0000_create_roles/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE roles;

migrations/2026-05-18-182143-0000_create_roles/up.sql

@@ -0,0 +1,7 @@
+-- Your SQL goes here
+CREATE TABLE roles (
+    id SERIAL PRIMARY KEY,
+    rolename TEXT NOT NULL,
+    groupname TEXT NOT NULL,
+    permission TEXT NOT NULL
+)