Seed data management in Supabase - Step-by-Step Execution

Process Flow - Seed data management

Start: Prepare seed data file

↓

Connect to Supabase DB

↓

Run seed script

↓

Check if tables exist

↓

Insert or update

↓

Insert seed data

↓

Verify data inserted

↓

End: Seed complete

This flow shows preparing seed data, connecting to the database, checking tables, inserting data, and verifying completion.

Execution Sample

Supabase

import { createClient } from '@supabase/supabase-js';

const supabase = createClient('url', 'key');

await supabase.from('users').insert([{ id: 1, name: 'Alice' }]);

This code connects to Supabase and inserts a user record into the 'users' table.

Process Table

Step	Action	Check/Query	Result	Next Step
1	Prepare seed data file	N/A	Seed data ready with users and products	Connect to Supabase DB
2	Connect to Supabase DB	Connection test	Connection successful	Check if tables exist
3	Check if 'users' table exists	Query table info	Table exists	Insert seed data
4	Insert seed data into 'users'	Insert query	1 row inserted	Verify data inserted
5	Verify data in 'users'	Select query	User Alice found	Check if 'products' table exists
6	Check if 'products' table exists	Query table info	Table does not exist	Create 'products' table
7	Create 'products' table	Create table query	Table created	Insert seed data into 'products'
8	Insert seed data into 'products'	Insert query	3 rows inserted	Verify data inserted
9	Verify data in 'products'	Select query	3 products found	Seed complete
10	Seed complete	N/A	All seed data inserted successfully	End

💡 All seed data inserted and verified, process ends.

Status Tracker

Variable	Start	After Step 4	After Step 8	Final
users_table_exists	undefined	true	true	true
products_table_exists	undefined	undefined	true	true
users_rows_inserted	0	1	1	1
products_rows_inserted	0	0	3	3

Key Moments - 3 Insights

Why do we check if tables exist before inserting seed data?

Because inserting data into a non-existent table causes errors. The execution_table rows 3 and 6 show checking tables before insertion.

What happens if the 'products' table does not exist during seeding?

The script creates the 'products' table first (row 7) before inserting data (row 8), ensuring no errors.

How do we verify that seed data was inserted correctly?

By running select queries after insertion (rows 5 and 9) to confirm the expected rows exist.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the 'users' table confirmed to exist?

A Step 6

B Step 4

C Step 3

D Step 7

💡 Hint

Check the 'Check if tables exist' actions in execution_table rows.

At which step does the seed script create a missing table?

A Step 5

B Step 7

C Step 8

D Step 9

💡 Hint

Look for 'Create table query' in the execution_table.

If the 'products' table already existed, which step would be skipped?

A Step 7

B Step 6

C Step 8

D Step 9

💡 Hint

Refer to variable_tracker and execution_table steps about table existence.

Concept Snapshot

Seed Data Management in Supabase:
- Prepare seed data as JSON or JS objects.
- Connect to Supabase using createClient(url, key).
- Check if tables exist before inserting.
- Create tables if missing.
- Insert seed data with from('table').insert(data).
- Verify insertion with select queries.

Full Transcript

Seed data management in Supabase involves preparing data files, connecting to the database, checking if required tables exist, creating them if needed, inserting the seed data, and verifying the data was inserted correctly. The process ensures no errors occur by confirming table existence before insertion. Verification queries confirm the seed data is present. This step-by-step approach helps maintain a reliable initial database state.