-
Notifications
You must be signed in to change notification settings - Fork 3
Supabase - new table - memory_emails #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sweetmantech
merged 2 commits into
main
from
sweetmantech/myc-3787-supabase-new-table-memory_emails
Dec 18, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
26 changes: 26 additions & 0 deletions
26
supabase/migrations/20251218123402_create_memory_emails_table.sql
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| -- Create memory_emails table | ||
| -- Stores the relationship between emails and memories | ||
|
|
||
| CREATE TABLE public.memory_emails ( | ||
| id uuid NOT NULL DEFAULT gen_random_uuid(), | ||
| email_id uuid NOT NULL, | ||
| memory uuid NOT NULL, | ||
| message_id text NOT NULL, | ||
| created_at timestamp with time zone NOT NULL DEFAULT now(), | ||
| CONSTRAINT memory_emails_pkey PRIMARY KEY (id), | ||
| CONSTRAINT memory_emails_email_id_unique UNIQUE (email_id), | ||
| CONSTRAINT memory_emails_message_id_unique UNIQUE (message_id), | ||
| CONSTRAINT memory_emails_memory_fkey FOREIGN KEY (memory) | ||
| REFERENCES memories(id) ON UPDATE CASCADE ON DELETE CASCADE | ||
| ) TABLESPACE pg_default; | ||
|
|
||
| -- Enable Row Level Security | ||
| ALTER TABLE public.memory_emails ENABLE ROW LEVEL SECURITY; | ||
|
sweetmantech marked this conversation as resolved.
|
||
|
|
||
| -- Create index on memory for faster lookups | ||
| CREATE INDEX IF NOT EXISTS memory_emails_memory_idx | ||
| ON public.memory_emails(memory); | ||
|
|
||
| -- Create index on created_at for sorting | ||
| CREATE INDEX IF NOT EXISTS memory_emails_created_at_idx | ||
| ON public.memory_emails(created_at); | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.