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.

Practice

1. What is the main purpose of seed data in a Supabase project?

easy

A. To delete all existing data from the database

B. To backup the database before changes

C. To add initial data automatically to the database

D. To monitor database performance

Solution

1. Step 1: Understand seed data concept

   Seed data is used to populate the database with initial or default data automatically.

2. Step 2: Identify the purpose in Supabase

   In Supabase, seed data helps set up consistent data for testing and development.

3. Final Answer:

   To add initial data automatically to the database -> Option C

4. Quick Check:

   Seed data = initial data setup [OK]

Hint: Seed data means initial data added automatically [OK]

Common Mistakes:

• Confusing seed data with backup or monitoring
• Thinking seed deletes data instead of adding
• Assuming seed data is for performance tuning

2. Which command runs seed scripts in a Supabase project?

easy

A. supabase db backup create

B. supabase db migrate run

C. supabase db reset

D. supabase db seed run

Solution

1. Step 1: Recall Supabase seed command

   The command to execute seed scripts is supabase db seed run.

2. Step 2: Differentiate from other commands

   supabase db migrate run applies migrations, not seeds; reset and backup are unrelated.

3. Final Answer:

   supabase db seed run -> Option D

4. Quick Check:

   Seed scripts run with supabase db seed run [OK]

Hint: Seed scripts run with 'supabase db seed run' command [OK]

Common Mistakes:

• Using migrate command instead of seed
• Confusing reset with seed run
• Trying backup commands for seeding

3. Given this seed script snippet in Supabase:

INSERT INTO users (id, name) VALUES (1, 'Alice'), (2, 'Bob');
INSERT INTO users (id, name) VALUES (3, 'Charlie');

What will be the total number of users after running the seed?

medium

A. 3

B. 2

C. 1

D. 4

Solution

1. Step 1: Count inserted rows in first statement

   The first INSERT adds 2 users: Alice and Bob.

2. Step 2: Count inserted rows in second statement

   The second INSERT adds 1 user: Charlie.

3. Step 3: Calculate total users inserted

   Total users = 2 + 1 = 3.

4. Final Answer:

   3 -> Option A

5. Quick Check:

   2 + 1 = 3 users inserted [OK]

Hint: Add all inserted rows to find total users [OK]

Common Mistakes:

• Counting only first INSERT statement
• Assuming duplicate rows overwrite
• Miscounting number of values per INSERT

4. You run supabase db seed run but get an error: duplicate key value violates unique constraint. What is the likely cause?

medium

A. Database connection is lost

B. Seed script tries to insert data with existing primary keys

C. Supabase CLI is not installed

D. Seed script syntax is incorrect

Solution

1. Step 1: Understand the error message

   The error means the seed script tries to insert rows with keys already in the database.

2. Step 2: Identify cause in seed data context

   Duplicate primary keys cause conflicts when inserting seed data multiple times without cleanup.

3. Final Answer:

   Seed script tries to insert data with existing primary keys -> Option B

4. Quick Check:

   Duplicate key error = duplicate primary keys in seed [OK]

Hint: Duplicate key error means repeated primary keys in seed data [OK]

Common Mistakes:

• Assuming syntax error causes duplicate key message
• Blaming CLI installation for data errors
• Ignoring database state before seeding

5. You want to seed a Supabase database with initial users but avoid duplicate entries if the seed runs multiple times. Which approach is best?

hard

A. Use INSERT ... ON CONFLICT DO NOTHING in seed scripts

B. Delete the entire database before each seed run

C. Run seed scripts only once manually

D. Use DROP TABLE users before inserting

Solution

1. Step 1: Understand the problem of duplicates

   Running seed multiple times can cause duplicate key errors if data already exists.

2. Step 2: Choose a safe insert method

   Using INSERT ... ON CONFLICT DO NOTHING skips inserting duplicates safely.

3. Step 3: Evaluate other options

   Deleting database or tables is risky and inefficient; running seed once is error-prone.

4. Final Answer:

   Use INSERT ... ON CONFLICT DO NOTHING in seed scripts -> Option A

5. Quick Check:

   Safe inserts prevent duplicates with ON CONFLICT [OK]

Hint: Use ON CONFLICT DO NOTHING to avoid duplicate inserts [OK]

Common Mistakes:

• Dropping tables can cause data loss
• Assuming seed runs only once always
• Deleting whole database is overkill