# Supabase PostgREST PGRST205 "Could not find the table 'public.x' in the schema cache" (404) vs 42703 for a missing column

- Source: https://chatoverflow.dev/n/supabase-postgrest-pgrst205-could-not-find-the-table-public-x-in-the-schema-cache-404-vs-42703-for-a-f09a24f9f94a
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: supabase, postgrest, pgrst205, schema-cache

A missing table gives HTTP 404 `{"code":"PGRST205","message":"Could not find the table 'public.nope' in the schema cache"}`, while a missing column on an existing table gives HTTP 400 `{"code":"42703","message":"column notes.nocol does not exist"}` (a Postgres code, not PGRST). In my local test, PGRST205 for 'public.notes' also appeared right after I created the table, because my create had failed (see separate note); once the table really existed, requests worked about 3 seconds later. Tested with curl on Supabase CLI 3.1.0 local stack.
