Data types and constraints in Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a column with a text data type in Supabase.

Supabase

CREATE TABLE users (username [1] NOT NULL);

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

AINTEGER

BVARCHAR(255)

CTEXT

DBOOLEAN

Attempts:

3 left

💡 Hint

Common Mistakes

Using INTEGER or BOOLEAN for text data.

Using VARCHAR without specifying length.

The TEXT data type stores variable-length strings in Supabase.

2fill in blank

medium

Complete the code to add a primary key constraint to the id column.

Supabase

CREATE TABLE products (id [1] PRIMARY KEY, name TEXT);

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

ASERIAL

BDATE

CTEXT

DBOOLEAN

Attempts:

3 left

💡 Hint

Common Mistakes

Using TEXT as a primary key without uniqueness.

Using BOOLEAN or DATE for id columns.

The SERIAL type auto-increments integers and is commonly used for primary keys.

3fill in blank

hard

Fix the error in the column definition to correctly enforce a NOT NULL constraint.

Supabase

CREATE TABLE orders (order_id INTEGER [1]);

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

AUNIQUE

BNULL

CDEFAULT NULL

DNOT NULL

Attempts:

3 left

💡 Hint

Common Mistakes

Using NULL or DEFAULT NULL which allow empty values.

Confusing UNIQUE with NOT NULL.

The NOT NULL constraint ensures the column cannot have empty values.

4fill in blank

hard

Fill both blanks to create a table with a unique email column and a created_at timestamp with default current time.

Supabase

CREATE TABLE users (email [1] UNIQUE, created_at [2] DEFAULT now());

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

ATEXT

BBOOLEAN

CTIMESTAMP

DINTEGER

Attempts:

3 left

💡 Hint

Common Mistakes

Using BOOLEAN or INTEGER for email or timestamp.

Forgetting UNIQUE constraint on email.

Email should be stored as TEXT and timestamps use TIMESTAMP type with default current time.

5fill in blank

hard

Fill all three blanks to define a table with an id primary key, a price column that cannot be negative, and a status column with a default value.

Supabase

CREATE TABLE items (id [1] PRIMARY KEY, price [2] CHECK (price >= 0), status [3] DEFAULT 'available');

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

ASERIAL

BNUMERIC

CTEXT

DBOOLEAN

Attempts:

3 left

💡 Hint

Common Mistakes

Using BOOLEAN for price or status.

Not using CHECK to prevent negative prices.

SERIAL is used for auto-increment id, NUMERIC for price with a check constraint, and TEXT for status with a default value.