Fix · Supabase and databases

"Database error saving new user" on sign-up

Blocks your work

What you may see

Sign-up fails with a database error
It started after I added a profile table or a trigger

Most likely cause

A trigger that runs when a user signs up (for example, to create a profile) fails, so the whole sign-up is cancelled.

Check first (about two minutes)

Do you have a function that runs after a new user is created? Open its code.
Check the Postgres logs at the time of the failure.

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
"Database error saving new user" on sign-up

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
A trigger that runs when a user signs up (for example, to create a profile) fails, so the whole sign-up is cancelled.

DO THESE STEPS, IN THIS ORDER
1. Find the trigger on the auth users table and the function it calls.
2. Read the logs to find the failing statement (often a missing column, a not-null value or a missing permission for the function).
3. Fix the function in a migration, keep it simple, make it safe to run twice, and give me a rollback file.
4. Test with a brand-new test email on a test copy.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A new test sign-up creates both the user and the profile.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete the auth tables or users.
- 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 trigger on the auth users table and the function it calls.
Read the logs to find the failing statement (often a missing column, a not-null value or a missing permission for the function).
Fix the function in a migration, keep it simple, make it safe to run twice, and give me a rollback file.
Test with a brand-new test email on a test copy.

Do not do this

Do not remove the trigger and leave users without profiles unnoticed.
Do not delete the auth tables or users.

Try another entry