From 7a9e229d5f4913d1a48c92615bcb3234f5dcfd33 Mon Sep 17 00:00:00 2001
From: Benedikt Peetz <benedikt.peetz@b-peetz.de>
Date: Thu, 11 Jun 2026 01:05:07 +0200
Subject: chore: Restore db migrations

---
 .../20231203124112_create-store.sql                     | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 crates/turtle/db/server-sqlite-migrations/20231203124112_create-store.sql

(limited to 'crates/turtle/db/server-sqlite-migrations/20231203124112_create-store.sql')

diff --git a/crates/turtle/db/server-sqlite-migrations/20231203124112_create-store.sql b/crates/turtle/db/server-sqlite-migrations/20231203124112_create-store.sql
new file mode 100644
index 00000000..ca19ed62
--- /dev/null
+++ b/crates/turtle/db/server-sqlite-migrations/20231203124112_create-store.sql
@@ -0,0 +1,17 @@
+create table store (
+	id text primary key,            -- remember to use uuidv7 for happy indices <3
+  client_id text not null,        -- I am too uncomfortable with the idea of a client-generated primary key, even though it's fine mathematically
+	host text not null,             -- a unique identifier for the host
+	idx bigint not null,       -- the index of the record in this store, identified by (host, tag)
+	timestamp bigint not null,      -- not a timestamp type, as those do not have nanosecond precision
+	version text not null,
+	tag text not null,              -- what is this? history, kv, whatever. Remember clients get a log per tag per host
+	data text not null,            -- store the actual history data, encrypted. I don't wanna know!
+	cek text not null,            
+
+	user_id bigint not null,        -- allow multiple users
+	created_at timestamp not null default current_timestamp
+);
+
+create unique index record_uniq ON store(user_id, host, tag, idx);
+
-- 
cgit v1.3.1

