Fix · Supabase and databases

relation "..." does not exist (42P01)

Not checked against the vendor's current screens

What you may see

The error says a table does not exist
It works locally and not on the live database

Most likely cause

The table name is spelled differently, lives in another schema, or the migration that creates it was never run on this database.

Check first (about two minutes)

Look at the table list in the dashboard of THIS project: is the table there with that exact name?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who knows Supabase (database, login and file storage) and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
relation "..." does not exist (42P01)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The table name is spelled differently, lives in another schema, or the migration that creates it was never run on this database.

DO THESE STEPS, IN THIS ORDER
1. Compare the table name in the code with the real list of tables (case matters when quoted).
2. Check which migration files exist and which ran on this database.
3. Give me the one migration file to run, plus its rollback; I will run it after a backup.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The query runs and returns rows or an empty list, not 42P01.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not create a table by guessing its columns.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Compare the table name in the code with the real list of tables (case matters when quoted).
Check which migration files exist and which ran on this database.
Give me the one migration file to run, plus its rollback; I will run it after a backup.

Do not do this

Do not run SQL on live data without a backup.
Do not create a table by guessing its columns.

Try another entry