-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsetup_supabase.sql
More file actions
38 lines (31 loc) · 1.47 KB
/
setup_supabase.sql
File metadata and controls
38 lines (31 loc) · 1.47 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
-- Create tables for chat memory storage in Supabase
-- Run this SQL in your Supabase SQL editor
-- Table for chat sessions
CREATE TABLE IF NOT EXISTS chat_sessions (
id TEXT PRIMARY KEY,
created_at TIMESTAMPTZ DEFAULT NOW(),
updated_at TIMESTAMPTZ DEFAULT NOW(),
metadata JSONB DEFAULT '{}'
);
-- Table for chat messages
CREATE TABLE IF NOT EXISTS chat_messages (
id TEXT PRIMARY KEY,
session_id TEXT REFERENCES chat_sessions(id) ON DELETE CASCADE,
message_type TEXT NOT NULL CHECK (message_type IN ('human', 'ai')),
content TEXT NOT NULL,
created_at TIMESTAMPTZ DEFAULT NOW(),
metadata JSONB DEFAULT '{}'
);
-- Create indexes for better performance
CREATE INDEX IF NOT EXISTS idx_chat_messages_session_id ON chat_messages(session_id);
CREATE INDEX IF NOT EXISTS idx_chat_messages_created_at ON chat_messages(created_at);
CREATE INDEX IF NOT EXISTS idx_chat_sessions_updated_at ON chat_sessions(updated_at);
-- Enable Row Level Security (optional but recommended)
ALTER TABLE chat_sessions ENABLE ROW LEVEL SECURITY;
ALTER TABLE chat_messages ENABLE ROW LEVEL SECURITY;
-- Create policies (adjust based on your auth requirements)
-- These are basic policies - customize based on your needs
CREATE POLICY "Users can manage their own sessions" ON chat_sessions
FOR ALL USING (true); -- Adjust this based on your auth setup
CREATE POLICY "Users can manage their own messages" ON chat_messages
FOR ALL USING (true); -- Adjust this based on your auth setup