← All errors · Supabase

relation "public.x" does not exist

Exact error

relation "public.profiles" does not exist

What it means

Postgres can't find the table or view. Error code 42P01.

Likely causes

• The migration that creates the table was never run on this project.
• Typo or case mismatch (tables created with quotes like "Profiles" are case-sensitive).
• Table lives in a different schema.

How to fix it

1. Check Table Editor or run:

   select table_schema, table_name
   from information_schema.tables
   where table_name ilike '%profile%';

2. Apply pending migrations with the Supabase CLI:

   supabase db push

3. Use lowercase, unquoted table names to avoid case issues.

Related errors

• Could not find the column in the schema cache