-- Users, chats, membership and messages. PostgreSQL is the source of truth. -- timestamptz(3): millisecond precision round-trips exactly through JS Date and keyset cursors. CREATE TABLE users ( id uuid PRIMARY KEY DEFAULT gen_random_uuid(), username text NOT NULL UNIQUE CHECK (username ~ '^[a-z0-9_]{3,32}$'), display_name text NOT NULL CHECK (char_length(display_name) BETWEEN 1 AND 100), password_hash text NOT NULL, created_at timestamptz(3) NOT NULL DEFAULT now() ); CREATE TABLE chats ( id uuid PRIMARY KEY DEFAULT gen_random_uuid(), title text NOT NULL CHECK (char_length(title) BETWEEN 1 AND 100), created_at timestamptz(3) NOT NULL DEFAULT now() ); CREATE TABLE chat_members ( chat_id uuid NOT NULL REFERENCES chats (id), user_id uuid NOT NULL REFERENCES users (id), PRIMARY KEY (chat_id, user_id) ); -- GET /chats: chats of one user. CREATE INDEX chat_members_user_idx ON chat_members (user_id, chat_id); CREATE TABLE messages ( id uuid PRIMARY KEY DEFAULT gen_random_uuid(), chat_id uuid NOT NULL, sender_id uuid NOT NULL, text text NOT NULL CHECK (char_length(text) BETWEEN 1 AND 4000), created_at timestamptz(3) NOT NULL DEFAULT now(), -- the sender must be a member of the chat; also covers chat/user existence FOREIGN KEY (chat_id, sender_id) REFERENCES chat_members (chat_id, user_id) ); -- History keyset: WHERE chat_id = $1 AND (created_at, id) > ($2, $3) ORDER BY created_at, id LIMIT $4. -- Choice justified in evidence/track2 (EXPLAIN ANALYZE on 200k messages). CREATE INDEX messages_chat_created_id_idx ON messages (chat_id, created_at, id);