CREATE TABLE attachments ( id uuid PRIMARY KEY, chat_id uuid NOT NULL REFERENCES chats(id) ON DELETE CASCADE, owner_id uuid NOT NULL REFERENCES users(id), filename text NOT NULL, object_key text NOT NULL UNIQUE, content_type text NOT NULL CHECK (content_type IN ('image/png','image/jpeg')), size_bytes bigint NOT NULL CHECK (size_bytes BETWEEN 1 AND 10485760), sha256 text NOT NULL CHECK (sha256 ~ '^[a-f0-9]{64}$'), status text NOT NULL DEFAULT 'ready' CHECK (status='ready'), created_at timestamptz NOT NULL DEFAULT clock_timestamp(), updated_at timestamptz NOT NULL DEFAULT clock_timestamp() ); CREATE INDEX attachments_chat_idx ON attachments(chat_id,created_at,id); -- Durable intent is committed BEFORE any S3 PUT. A crashed upload remains -- visible to the cleanup process even if its ready metadata never committed. CREATE TABLE attachment_uploads ( id uuid PRIMARY KEY, object_key text NOT NULL UNIQUE, created_at timestamptz NOT NULL DEFAULT clock_timestamp() ); CREATE INDEX attachment_uploads_created_idx ON attachment_uploads(created_at); ALTER TABLE messages DROP CONSTRAINT messages_text_check; ALTER TABLE messages ADD CONSTRAINT messages_text_check CHECK (char_length(text)<=4000); ALTER TABLE messages ADD COLUMN attachment_ids uuid[] NOT NULL DEFAULT '{}'; ALTER TABLE messages ADD CONSTRAINT messages_body_check CHECK (char_length(btrim(text))>0 OR cardinality(attachment_ids)>0); ALTER TABLE messages ADD CONSTRAINT messages_attachments_limit CHECK (cardinality(attachment_ids)<=10);