How to Delete Records in Supabase

1import { supabase } from '@/lib/supabase'
2
3// Delete a single task by ID
4const { error } = await supabase
5  .from('tasks')
6  .delete()
7  .eq('id', 42)
8
9if (error) {
10  console.error('Delete failed:', error.message)
11} else {
12  console.log('Task deleted successfully')
13}
14
15// Delete and return the deleted row
16const { data, error: err } = await supabase
17  .from('tasks')
18  .delete()
19  .eq('id', 42)
20  .select()
21
22console.log('Deleted row:', data)

1// Delete multiple tasks by ID
2const { error } = await supabase
3  .from('tasks')
4  .delete()
5  .in('id', [10, 11, 12, 13])
6
7// Delete all completed tasks for the current user
8const { data: { user } } = await supabase.auth.getUser()
9const { error: bulkError } = await supabase
10  .from('tasks')
11  .delete()
12  .eq('user_id', user.id)
13  .eq('completed', true)
14
15// Delete old records (older than 30 days)
16const thirtyDaysAgo = new Date(Date.now() - 30 * 24 * 60 * 60 * 1000).toISOString()
17const { error: cleanupError } = await supabase
18  .from('logs')
19  .delete()
20  .lt('created_at', thirtyDaysAgo)

1-- Enable RLS (if not already enabled)
2ALTER TABLE public.tasks ENABLE ROW LEVEL SECURITY;
3
4-- Allow users to delete their own tasks
5CREATE POLICY "Users can delete own tasks"
6  ON public.tasks
7  FOR DELETE
8  TO authenticated
9  USING ((SELECT auth.uid()) = user_id);
10
11-- You also need a SELECT policy for delete to find rows
12CREATE POLICY "Users can view own tasks"
13  ON public.tasks
14  FOR SELECT
15  TO authenticated
16  USING ((SELECT auth.uid()) = user_id);

1-- Create a table with cascading delete on the foreign key
2CREATE TABLE public.comments (
3  id bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
4  task_id bigint REFERENCES public.tasks(id) ON DELETE CASCADE,
5  user_id uuid REFERENCES auth.users(id) ON DELETE CASCADE,
6  body text NOT NULL,
7  created_at timestamptz DEFAULT now()
8);
9
10-- To change an existing foreign key to cascade:
11-- 1. Drop the old constraint
12ALTER TABLE public.comments
13  DROP CONSTRAINT comments_task_id_fkey;
14
15-- 2. Add it back with CASCADE
16ALTER TABLE public.comments
17  ADD CONSTRAINT comments_task_id_fkey
18  FOREIGN KEY (task_id) REFERENCES public.tasks(id) ON DELETE CASCADE;

1-- Add soft-delete column to existing table
2ALTER TABLE public.tasks
3  ADD COLUMN deleted_at timestamptz DEFAULT null;
4
5-- Update RLS policy to hide soft-deleted rows
6DROP POLICY IF EXISTS "Users can view own tasks" ON public.tasks;
7CREATE POLICY "Users can view own active tasks"
8  ON public.tasks FOR SELECT
9  TO authenticated
10  USING ((SELECT auth.uid()) = user_id AND deleted_at IS NULL);
11
12-- Soft-delete from the JS client (UPDATE, not DELETE)
13-- const { error } = await supabase
14--   .from('tasks')
15--   .update({ deleted_at: new Date().toISOString() })
16--   .eq('id', 42)