Why optimization prevents slow queries in Supabase - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select all columns from the users table.

Supabase

SELECT [1] FROM users;

Drag options to blanks, or click blank then click option'

A*

Bid

Cemail

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting only one column when all are needed.

Using column names without quotes.

The asterisk (*) selects all columns from the table, which is the simplest way to retrieve all data.

2fill in blank

medium

Complete the code to filter users with age greater than 30.

Supabase

SELECT * FROM users WHERE age [1] 30;

Drag options to blanks, or click blank then click option'

A<=

B=

C<

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' which filters for ages less than 30.

Using '=' which filters for age exactly 30.

The '>' operator filters rows where age is greater than 30, which matches the requirement.

3fill in blank

hard

Fix the error in the query to count users grouped by country.

Supabase

SELECT country, COUNT(*) [1] users GROUP BY country;

Drag options to blanks, or click blank then click option'

AIN

BON

CFROM

DWHERE

Attempts:

3 left

💡 Hint

Common Mistakes

Using WHERE instead of FROM causes syntax errors.

Using ON or IN in place of FROM is incorrect here.

The FROM keyword specifies the table to select data from, which is required before GROUP BY.

4fill in blank

hard

Fill both blanks to optimize the query by indexing the age column and filtering efficiently.

Supabase

CREATE INDEX [1] ON users([2]);

Drag options to blanks, or click blank then click option'

Aidx_users_age

Bage

Cname

Demail

Attempts:

3 left

💡 Hint

Common Mistakes

Indexing columns not used in filters does not improve query speed.

Using invalid index names causes errors.

Creating an index named 'idx_users_age' on the 'age' column speeds up queries filtering by age.

5fill in blank

hard

Fill all three blanks to write a query that selects user names, filters by age greater than 25, and orders results by name ascending.

Supabase

SELECT [1] FROM users WHERE age [2] 25 ORDER BY [3] ASC;

Drag options to blanks, or click blank then click option'

Aname

B>

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Ordering by age instead of name changes the output order.

Using '<' instead of '>' filters the wrong age group.

Selecting 'name', filtering with '>' for age, and ordering by 'name' ascending produces the desired result efficiently.

Practice

1. Why is optimization important for database queries in Supabase?

easy

A. It deletes unnecessary tables automatically.

B. It helps queries run faster by finding data quickly.

C. It makes the database store more data.

D. It changes the database type to NoSQL.

Solution

1. Step 1: Understand query speed

   Queries that are not optimized take longer to find data, causing delays.

2. Step 2: Role of optimization

   Optimization helps the database find data faster, improving query speed.

3. Final Answer:

   It helps queries run faster by finding data quickly. -> Option B

4. Quick Check:

   Optimization = faster queries [OK]

Hint: Optimization means faster data finding [OK]

Common Mistakes:

• Thinking optimization stores more data
• Believing optimization deletes tables
• Confusing optimization with changing database type

2. Which of the following is the correct way to add an index in Supabase SQL to speed up queries on the column user_id?

easy

A. CREATE INDEX ON users (user_id);

B. ADD INDEX users user_id;

C. INDEX CREATE users.user_id;

D. MAKE INDEX users ON user_id;

Solution

1. Step 1: Recall SQL syntax for index creation

   The correct SQL command to create an index is CREATE INDEX index_name ON table_name(column_name); but index_name can be omitted for default naming.

2. Step 2: Match syntax to options

   CREATE INDEX ON users (user_id); uses the correct syntax: CREATE INDEX ON users (user_id); which is valid in PostgreSQL (used by Supabase).

3. Final Answer:

   CREATE INDEX ON users (user_id); -> Option A

4. Quick Check:

   Correct SQL syntax = CREATE INDEX ON users (user_id); [OK]

Hint: Use CREATE INDEX ON table (column) [OK]

Common Mistakes:

• Using ADD INDEX which is MySQL syntax
• Incorrect order of keywords
• Missing parentheses around column name

3. Given this Supabase SQL query:

SELECT * FROM orders WHERE customer_id = 123;

and an index exists on customer_id, what is the expected effect on query performance?

medium

A. The query will cause an error if an index exists.

B. The query will run slower because indexes add overhead.

C. The query will return no results because indexes filter data.

D. The query will run faster because the index helps find rows quickly.

Solution

1. Step 1: Understand index purpose

   An index on customer_id helps the database find matching rows faster without scanning the whole table.

2. Step 2: Effect on query

   Because the query filters by customer_id, the index speeds up the search, improving performance.

3. Final Answer:

   The query will run faster because the index helps find rows quickly. -> Option D

4. Quick Check:

   Index on filter column = faster query [OK]

Hint: Index on filter column speeds query [OK]

Common Mistakes:

• Thinking indexes slow down SELECT queries
• Believing indexes filter out data
• Assuming indexes cause errors

4. You run EXPLAIN ANALYZE SELECT * FROM products WHERE category = 'books'; in Supabase and notice the query is slow. Which of these is the best fix?

medium

A. Restart the Supabase server.

B. Delete the products table and recreate it.

C. Add an index on the category column.

D. Change the query to SELECT all columns without WHERE.

Solution

1. Step 1: Analyze slow query cause

   The slow query filters by category but likely scans the whole table because no index exists.

2. Step 2: Apply optimization fix

   Adding an index on category lets the database quickly find matching rows, speeding up the query.

3. Final Answer:

   Add an index on the category column. -> Option C

4. Quick Check:

   Index on filter column fixes slow query [OK]

Hint: Add index on slow filter column [OK]

Common Mistakes:

• Deleting tables unnecessarily
• Removing WHERE clause which slows queries
• Restarting server without fixing query

5. You have a large sales table with millions of rows. Queries filtering by region are slow. You add an index on region but queries remain slow. What is the best next step to optimize queries in Supabase?

hard

A. Use EXPLAIN ANALYZE to check if the index is used and adjust the query or index accordingly.

B. Drop the index because it does not help and slows inserts.

C. Add indexes on every column in the table.

D. Switch the database to a NoSQL system.

Solution

1. Step 1: Verify index usage with EXPLAIN ANALYZE

   Using EXPLAIN ANALYZE shows if the query planner uses the index or not, revealing why queries remain slow.

2. Step 2: Adjust query or index based on analysis

   If the index is not used, you may need to rewrite the query or create a different type of index to improve performance.

3. Final Answer:

   Use EXPLAIN ANALYZE to check if the index is used and adjust the query or index accordingly. -> Option A

4. Quick Check:

   Check index use before changing strategy [OK]

Hint: Check index use with EXPLAIN ANALYZE [OK]

Common Mistakes:

• Dropping useful indexes too soon
• Adding too many indexes causing overhead
• Switching database without analysis