relation "users" does not exist

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.

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

Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

Use this when

• You see this exact message or symptom in Metabase: Metabase saved question failed: ERROR relation does not exist for table in dashboard card query
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Metabase fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Metabase admin panel, the question page, and the serialization export log and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the saved question SQL or query builder definition, the dashboard parameter mapping, the database connection, and the collection the entity belongs to, and check the current listing of the named objects, the old versus new id or name, and the remapped reference in the config. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Verify: the corrected value or setting is visible in Metabase itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the card from the dashboard, run its question alone, fix the query or mapping, then reload the dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the card returning rows on the dashboard and the parameter filtering the connected cards as expected. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Metabase version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does metabase saved question failed: ERROR relation does not exist for table in dashboard card query keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Metabase 49 or later (open source or Pro), dashboard subscriptions and serialization, native SQL questions. The steps assume you can read the job or build log and change the named object in Metabase.

Why it happens

In Metabase, this failure usually means the reference the job uses points at an object that was renamed, merged, moved, or never created in this workspace, so the lookup returns nothing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

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

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

Thread query: Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

TL;DR: Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.