-- AGENT: Single versioned baseline migration for lab 2. The application records -- applied versions in schema_migrations, so rerunning it never duplicates rows. -- The unique username constraint is the authoritative defence against the -- concurrent-registration race, not a SELECT followed by an INSERT. CREATE TABLE IF NOT EXISTS users ( id uuid PRIMARY KEY, username text NOT NULL, display_name text NOT NULL, password_hash text NOT NULL, created_at timestamptz NOT NULL, CONSTRAINT users_username_key UNIQUE (username), CONSTRAINT users_username_format CHECK (username ~ '^[a-z0-9_]{3,32}$'), CONSTRAINT users_display_name_len CHECK (char_length(display_name) BETWEEN 1 AND 100) ); CREATE TABLE IF NOT EXISTS chats ( id uuid PRIMARY KEY, title text NOT NULL, created_at timestamptz NOT NULL, CONSTRAINT chats_title_len CHECK (char_length(title) BETWEEN 1 AND 100) ); CREATE TABLE IF NOT EXISTS chat_members ( chat_id uuid NOT NULL REFERENCES chats(id) ON DELETE CASCADE, user_id uuid NOT NULL REFERENCES users(id) ON DELETE RESTRICT, PRIMARY KEY (chat_id, user_id) ); CREATE INDEX IF NOT EXISTS chat_members_user_idx ON chat_members (user_id, chat_id); CREATE TABLE IF NOT EXISTS messages ( id uuid PRIMARY KEY, chat_id uuid NOT NULL REFERENCES chats(id) ON DELETE CASCADE, sender_id uuid NOT NULL REFERENCES users(id) ON DELETE RESTRICT, text text NOT NULL, created_at timestamptz NOT NULL, CONSTRAINT messages_text_len CHECK (char_length(text) BETWEEN 1 AND 4000) ); -- AGENT: This composite index matches the only history predicate and sort order: -- (chat_id, created_at, id). It lets each keyset page seek directly to the cursor -- instead of scanning the chat history from the beginning. CREATE INDEX IF NOT EXISTS messages_chat_created_id_idx ON messages (chat_id, created_at, id);