PostgreSQL error 42P01 (Undefined Table) explained: what it means, why it happens, and how to fix it — with copy-paste code examples.
List tables with \dt or information_schema.tables to confirm the name. If that does not apply, schema-qualify the table (schema.table) to avoid search_path ambiguity — the full checklist is below.
SQLSTATE: 42P01
Official name: Undefined Table
Service: PostgreSQL
The referenced table does not exist in the current schema search path.
SELECT schemaname, tablename
FROM pg_tables
WHERE tablename ILIKE '%order%';Search pg_tables by name to confirm spelling, schema, and existence before assuming a missing migration.
Run migrations and check db_table on the model Meta.
class Meta:
db_table = 'orders' # match exactlyEnsure __tablename__ matches and the engine URL targets the right DB.
class Order(Base):
__tablename__ = 'orders'Confirm the table exists in the project and that the key/role has access.
const { error } = await supabase.from('orders').select('*')
// verify table name + schema in DashboardMost often this happens when misspelling the table name or using the wrong case, or when querying a table in the wrong schema due to search_path.
List tables with \dt or information_schema.tables to confirm the name.
This page documents fixes for: django, sqlalchemy, supabase.
Recommendations are editorial — DB Error Reference takes no payment or affiliate fees for tool listings.
This page is based on the official PostgreSQL documentation linked below and adds practical troubleshooting guidance on top.