Bird
Raised Fist0
Supabasecloud~10 mins

Creating tables via dashboard in Supabase - Interactive Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to create a new table named 'customers' in Supabase dashboard.

Supabase
CREATE TABLE [1] (id SERIAL PRIMARY KEY, name TEXT);
Drag options to blanks, or click blank then click option'
Acustomers
Borders
Cproducts
Dsales
Attempts:
3 left
💡 Hint
Common Mistakes
Using a different table name than 'customers'.
Confusing table names with column names.
2fill in blank
medium

Complete the code to add a column for storing email addresses as text.

Supabase
ALTER TABLE customers ADD COLUMN [1] TEXT;
Drag options to blanks, or click blank then click option'
Aaddress
Bphone
Cemail
Dage
Attempts:
3 left
💡 Hint
Common Mistakes
Using unrelated column names like 'phone' or 'age'.
Forgetting to specify the data type.
3fill in blank
hard

Fix the error in the code to create a table with a primary key.

Supabase
CREATE TABLE orders (order_id [1] PRIMARY KEY, order_date DATE);
Drag options to blanks, or click blank then click option'
ATEXT
BINTEGER
CVARCHAR
DSERIAL
Attempts:
3 left
💡 Hint
Common Mistakes
Using TEXT or VARCHAR for primary keys without auto-increment.
Using INTEGER without auto-increment.
4fill in blank
hard

Fill both blanks to create a table 'products' with an integer primary key and a text column 'product_name'.

Supabase
CREATE TABLE products (product_id [1] PRIMARY KEY, [2] TEXT);
Drag options to blanks, or click blank then click option'
ASERIAL
Bproduct_name
Cname
DINTEGER
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'INTEGER' without auto-increment for primary key.
Using wrong column name for product name.
5fill in blank
hard

Fill all three blanks to create a table 'employees' with an auto-increment primary key, a text column 'first_name', and a date column 'hire_date'.

Supabase
CREATE TABLE employees (employee_id [1] PRIMARY KEY, [2] TEXT, [3] DATE);
Drag options to blanks, or click blank then click option'
ASERIAL
Bfirst_name
Chire_date
DINTEGER
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'INTEGER' instead of 'SERIAL' for primary key.
Mixing up column names or data types.

Practice

(1/5)
1. What is the main purpose of creating tables via the Supabase dashboard?
easy
A. To deploy applications directly from the dashboard
B. To write complex SQL queries manually
C. To create user interface designs
D. To organize data with clear columns and constraints without coding

Solution

  1. Step 1: Understand the dashboard's role

    The Supabase dashboard allows users to create tables visually without writing code.
  2. Step 2: Identify the main benefit

    This method helps organize data clearly with columns and constraints easily set up.
  3. Final Answer:

    To organize data with clear columns and constraints without coding -> Option D
  4. Quick Check:

    Dashboard table creation = Organize data visually [OK]
Hint: Dashboard tables = visual data organization, no code needed [OK]
Common Mistakes:
  • Confusing dashboard with SQL query writing
  • Thinking dashboard creates app UI
  • Assuming dashboard deploys apps
2. Which step is required to add a new column when creating a table in the Supabase dashboard?
easy
A. Run a database migration script
B. Write a SQL INSERT statement
C. Click 'Add Column' and define the column name and type
D. Upload a CSV file with column data

Solution

  1. Step 1: Locate the column addition feature

    In the Supabase dashboard, you add columns by clicking the 'Add Column' button.
  2. Step 2: Define column details

    After clicking, you specify the column name and data type to create it.
  3. Final Answer:

    Click 'Add Column' and define the column name and type -> Option C
  4. Quick Check:

    Add column = Click button + define name/type [OK]
Hint: Add columns by clicking 'Add Column' and setting details [OK]
Common Mistakes:
  • Confusing column addition with data insertion
  • Trying to upload data instead of defining structure
  • Running scripts instead of using dashboard UI
3. After creating a table with columns id (integer, primary key) and name (text) via the Supabase dashboard, what will be the result of inserting {id: 1, name: 'Alice'} and then querying all rows?
medium
A. [{id: 1, name: 'Alice'}]
B. Error: Missing table schema
C. Empty result set
D. [{name: 'Alice'}]

Solution

  1. Step 1: Understand table schema and insert

    The table has columns 'id' as primary key and 'name' as text. Inserting {id:1, name:'Alice'} matches schema.
  2. Step 2: Query all rows after insert

    Querying all rows returns the inserted row as [{id: 1, name: 'Alice'}].
  3. Final Answer:

    [{id: 1, name: 'Alice'}] -> Option A
  4. Quick Check:

    Insert + query = inserted row returned [OK]
Hint: Insert matching schema, query returns inserted rows [OK]
Common Mistakes:
  • Expecting error without schema mismatch
  • Thinking query returns empty before insert
  • Assuming partial row returned without id
4. You tried to create a table via the Supabase dashboard but received an error saying the column name is invalid. What is the most likely cause?
medium
A. Not selecting a data type for the column
B. Using spaces or special characters in the column name
C. Adding too many columns at once
D. Not clicking the 'Save' button after creation

Solution

  1. Step 1: Identify invalid column name causes

    Column names cannot contain spaces or special characters in Supabase.
  2. Step 2: Recognize common naming rules

    Valid names use letters, numbers, and underscores only.
  3. Final Answer:

    Using spaces or special characters in the column name -> Option B
  4. Quick Check:

    Invalid column name = spaces/special chars [OK]
Hint: Use only letters, numbers, underscores in column names [OK]
Common Mistakes:
  • Ignoring naming rules and using spaces
  • Forgetting to select data type (usually warned separately)
  • Assuming too many columns cause naming errors
5. You want to create a table for customer orders with columns: order_id (primary key), customer_id, order_date, and total_amount. Which approach via the Supabase dashboard ensures data integrity and efficient queries?
hard
A. Set order_id as primary key, customer_id as foreign key, and choose appropriate data types
B. Create all columns as text type for flexibility
C. Skip primary key to allow duplicate orders
D. Add only order_id and total_amount columns

Solution

  1. Step 1: Define primary key for uniqueness

    Setting order_id as primary key ensures each order is unique.
  2. Step 2: Use foreign key and proper data types

    Defining customer_id as foreign key links orders to customers; choosing correct data types improves query efficiency.
  3. Final Answer:

    Set order_id as primary key, customer_id as foreign key, and choose appropriate data types -> Option A
  4. Quick Check:

    Primary + foreign keys + data types = data integrity [OK]
Hint: Use keys and correct types for integrity and speed [OK]
Common Mistakes:
  • Using text for all columns losing type benefits
  • Skipping primary key causing duplicates
  • Ignoring foreign key relationships
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard