when I try to sign in via magic link I get the error

duplicate key value violates unique constraint "users_pkey"

Hello @hanako! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.

Do you have a trigger function on auth.users to add to another table?

yeah I added it from here https://github.com/supabase/supabase/discussions/306#discussioncomment-138602

but no difference?

I still get the same error

I glanced at the first post there and that also triggers on update which won't work with just an insert to your public table. SignUp will insert to the auth.users table then when magic link is confirmed update it. That function triggers on both and tries to insert again and can't. The function is not good.

What I want to accomplish is : I have created user, post etc in prisma schema. when I login through magic link let's say, it shows up in authentication>users but not in table>editor>all tables>users. I want supabase-auth users to show up in prisma users

That is fine, you just can't call that function on an update. Just insert. Otherwise you need more logic.

this was marked as answer so I just pasted it and ran in sql editor

https://supabase.com/docs/guides/auth/managing-user-data#advanced-techniques is the SB guide on that type of function

so which one? 😅

Is your trigger just insert like shown in your last picture, or does it include update also?

I just copy pasted this code into the editor

You have a table called users in public?

yes

The error is saying you are trying to insert the same ID twice which is illegal for a primary key (hence my concern about update, but you show only an insert trigger, which is good). You also have the table declared public.users in the function, so it should not get confused with auth.users.

🥲

In your model you also have email as unique. Is it possible you are reusing the email for different tries and the old user still exists in your public.users table?

I am reusing for trying but it doesn't exist in public.users table. that and all prisma defined tables are empty as I haven't set up anything yet. tho when it worked two days ago the user would show up in auth.users

If you go to the dashboard/database/triggers you can remove the trigger. (You will have to rerun the last part of the sql again later to redo it). If you remove the trigger see if you can signIn a user.

its the second one right?

Could be your problem if they both trigger

ok im deleting 2nd

For what you started this with, the fix is to only have one trigger on auth.users calling the function.

yea I had tried adding triggers in editor but didn't delete them

Can you show me your current trigger

oh I dont have any I think

So you got rid of the trigger than called your signup_copy..... function and it appears you have another function handle_new_user_public that probably does no insert email.

oh so should I remove the

on_auth_user_created

trigger and add the one I deleted earlier?

YES

this one is default? I think. I didn't add it

There is no default.

cool

If you have further issues, start a new thread, I'm gone for a bit and you are not likely to get views in this one after this many posts. Good Luck.

it works now. the user shows up in both auth and public and also shows email!

Thread was archived by @hanako. Anyone can send a message to unarchive it.