Seed data management in Supabase - Time & Space Complexity

Time Complexity: Seed data management

O(1)

Understanding Time Complexity

When adding initial data to a database, it is important to know how the time to complete this task grows as the amount of data grows.

We want to understand how the number of operations changes when we increase the seed data size.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Insert multiple seed records into a table
const seedData = [
  { name: 'Alice', age: 30 },
  { name: 'Bob', age: 25 },
  // ... more records
];

const { data, error } = await supabase
  .from('users')
  .insert(seedData);

This code inserts a list of user records into the database all at once.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: One API call to insert all seed records in bulk.
• How many times: Exactly one call regardless of the number of records.

How Execution Grows With Input

As the number of seed records grows, the single insert call handles more data, but the number of calls stays the same.

Input Size (n)	Approx. API Calls/Operations
10	1 call with 10 records
100	1 call with 100 records
1000	1 call with 1000 records

Pattern observation: The number of API calls does not increase with more data; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means the number of API calls stays the same no matter how many records you insert at once.

Common Mistake

[X] Wrong: "Inserting more seed records means more API calls and longer time linearly."

[OK] Correct: Because the insert is done in bulk with one call, the number of calls does not grow with data size.

Interview Connect

Understanding how bulk operations affect time complexity helps you design efficient data loading processes and shows you can think about scaling in real projects.

Self-Check

"What if we inserted each seed record with a separate API call? How would the time complexity change?"

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