Fix · Supabase and databases

"JSON object requested, multiple (or no) rows returned" (PGRST116)

What you may see

My query for one record fails with an error
The page breaks when the record does not exist yet

Most likely cause

The code asked for exactly one row (single), but the query found none or more than one.

Check first (about two minutes)

Run the same filter in the SQL editor: how many rows come back?
If zero: does the row exist for this user, or does a row-level security rule hide it?

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.

THE PROBLEM
"JSON object requested, multiple (or no) rows returned" (PGRST116)

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 code asked for exactly one row (single), but the query found none or more than one.

DO THESE STEPS, IN THIS ORDER
1. Find the query and the filter it uses.
2. If "no row" is a normal case (a new user), use the variant that allows zero rows (maybeSingle) and handle null in the page.
3. If it returns more than one, find why (a missing unique rule) and add a unique constraint through a migration after checking existing data.
4. If a security rule hides the row, follow the empty-result entry.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The page shows its empty state without crashing, and a real record still loads.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete duplicate rows without showing me which ones.
- 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

Find the query and the filter it uses.
If "no row" is a normal case (a new user), use the variant that allows zero rows (maybeSingle) and handle null in the page.
If it returns more than one, find why (a missing unique rule) and add a unique constraint through a migration after checking existing data.
If a security rule hides the row, follow the empty-result entry.

Do not do this

Do not hide the error with an empty catch block.
Do not delete duplicate rows without showing me which ones.

Try another entry