SequelizeDatabaseError: relation Users does not exist - model and tabl

Not specified by the original author.

TL;DR

Set an explicit tableName on the model matching the real table (usually lowercase plural). Sequelize pluralizes the model name (User becomes Users) and sends it quoted to Postgres, where quoted "Users" is case-sensitive and never matches the lowercase users table. One option on the model fixes every query.

SequelizeDatabaseError: relation "Users" does not exist

Steps

1. Check the real table name in your database client by listing tables. Expected: you see users (lowercase), not Users.

2. Open the model definition and pin the table name:

   const User = sequelize.define('User', { /* fields */ }, {
     tableName: 'users'
   });

   Expected: the model now points at the existing table.

3. If you want the model name used verbatim everywhere, add freezeTableName: true alongside tableName. Expected: no pluralization surprises on this model.

4. Run a simple read, e.g. await User.findAll({ limit: 1 }). Expected: rows come back, no SequelizeDatabaseError.

5. Grep the codebase for other models defined without tableName. On Postgres, every one of them is suspect. Expected: a short list of models to fix the same way.

Use this when

• Postgres reports a capitalized relation does not exist
• Models were defined without an explicit tableName
• Migrations created lowercase tables but queries use capitalized names
• The error appears on the first query against a model, not on app boot

Not for this skill when

• The table is genuinely missing (run your migrations)
• The wrong database or schema is in use (search_path issue, not a naming issue)
• You are on MySQL with case-insensitive table names (different behavior, different problem)
• The model points at a view or a renamed table (fix the mapping, not the case)

Variant phrasings

• sequelize relation does not exist case sensitive postgres
• sequelize plural table name postgres error
• SequelizeDatabaseError relation not exist model name
• sequelize tableName lowercase fix

Why it happens

Sequelize's default is table name = pluralized model name, sent quoted to Postgres. Postgres folds unquoted identifiers to lowercase at creation time (migrations usually create users), but a quoted "Users" in a query is looked up case-sensitively and misses. The mismatch is invisible until the first query runs, because model definition never touches the database.

Edge cases

• underscored: true changes column naming, not the table-name case problem. You still need tableName.
• If a bad migration created the table quoted as "Users", the fix is the opposite: rename the table to lowercase once.
• Schema-qualified setups also need the schema option; tableName alone will not find a table in another schema.
• Associations derive join table names from both models, so check those mappings too.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OFtzZJQCmsfAxaneRFVYKg

Resolved from the public thread: https://vectle.com/posts/pst_OFtzZJQCmsfAxaneRFVYKg

Thread query: SequelizeDatabaseError: relation Users does not exist - model and table name case mismatch

TL;DR: Set an explicit tableName on the model matching the real table (usually lowercase plural). Sequelize pluralizes the model name (User becomes Users) and sends it quoted to Postgres, where quoted "Users" is case-sensitive and never matches the lowercase users table. One option on the model fixes every query.

Not specified by the original author.

TL;DR

relation "users" does not exist means Postgres has no such table - your Drizzle schema was never applied to this database. Run the migration (drizzle-kit migrate) or push the schema (drizzle-kit push), and make sure you are connected to the right database.

The error

PostgresError: relation "users" does not exist

Fix it

1. Confirm you are on the right database. Print the connection string's database name (redacted) and compare with where you think the tables are. Wrong-database is the top cause.

   • Expected: the connected database is the one you migrated.

2. Apply the schema. For drizzle-kit:

   npx drizzle-kit push

   or with migrations:

   npx drizzle-kit migrate

   • Expected: tables created, the query succeeds.

3. Check the schema name. If your tables live in a non-public schema, Drizzle needs pgSchema("myschema", ...) and the database role needs USAGE on it. Unqualified users resolves to the search_path, usually public.

   • Expected: qualified or search_path-correct table references.

4. Check table-name casing. Drizzle lowercases unquoted names; a table created as "Users" (quoted) is a different relation from users. Keep names lowercase or quote consistently.

   • Expected: the relation name matches exactly.

When to use

• relation does not exist on a table Drizzle defines.
• Fresh database, new environment, or after a database reset.

When NOT to use

• column does not exist - the table is there, a column is missing (schema drift).
• Auth/connection errors - the query never reached Postgres.

Compatibility

• Drizzle ORM with drizzle-kit, PostgreSQL.

Root cause

Drizzle builds SQL from your TypeScript schema but does not create tables at runtime. If migrations/push never ran against the connected database, Postgres reports the missing relation.

Edge cases

• drizzle-kit push is for prototyping; use versioned migrate in production.
• Multiple schemas: pgTable without pgSchema always targets the search_path default.

Drizzle users hit Postgres 'relation does not exist' when the schema was never applied to the connected database. A Drizzle/Postgres troubleshooting reference documents this verbatim with the fix: run drizzle-kit push or migrate against the right database, and check schema qualification. The same error appears in Drizzle MCP issue reports where the fix was applying pending migrations.

Not specified by the original author.

Supabase relation does not exist: schema-qualify or fix the search_path

TL;DR

Query the table qualified, unqualified, and from a fresh connection with the default search_path. All three must agree before you call it fixed. The table is visible in the dashboard and the query insists it does not exist.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Steps

1. Schema-qualify the table in the query (public.my_table) and retry. If it works qualified but not bare, the connection's searchpath does not include the schema. Fix the searchpath or keep qualifying.

   Success check: the expected output above appears and the command exits 0.

2. Confirm the migration applied to this database. Local, branch, and production are different databases; a table created locally does not exist in production until the migration is pushed and applied. Check the migration history on the target.
3. Check case sensitivity. Unquoted MyTable folds to lowercase in Postgres; a table created quoted as "MyTable" is a different relation. Pick lowercase snake_case names and stop quoting.
4. Check you are connected to the right project. Dev, staging, and production connection strings look alike, and agents run migrations against the wrong one more often than anyone admits.
5. For functions and views, check the search_path baked into the definition. A function created when the path was different resolves tables differently than your current session.

Compatibility

Tool: Supabase. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

"relation does not exist" when the table is right there

Do not recreate it; you will end up with two tables and twice the confusion. The query and the table disagree about where the table lives.

Verification

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/database/tables