silentworks
10/03/2021, 2:08 AMlarryM
10/03/2021, 3:55 AMNine
10/03/2021, 12:07 PMNine
10/03/2021, 12:07 PMeverconfusedguy
10/03/2021, 12:40 PMAnishDe12020
10/03/2021, 2:12 PMsilentworks
10/03/2021, 2:47 PManand
10/03/2021, 3:43 PMauth.role()
to something else?baptisteArno
10/03/2021, 3:44 PMsilentworks
10/03/2021, 3:50 PMHarryET
10/03/2021, 4:19 PMsilentworks
10/03/2021, 4:56 PMjavorszky
10/03/2021, 5:12 PMsupabase.auth.signUp
using an email address and password for an account that already exists, I get back a 400 status code, which is expected, but the error message is Thanks for registering, now check your email to complete the process."
, which is not what I expect it to be. Am I missing something, or is that a bug ?silentworks
10/03/2021, 6:42 PMshuckle
10/03/2021, 6:51 PMshuckle
10/03/2021, 6:51 PMNine
10/03/2021, 7:22 PMsilentworks
10/03/2021, 8:07 PMchasers
10/04/2021, 1:28 AMLeoSonnekus
10/04/2021, 4:13 AMAnishDe12020
10/04/2021, 4:18 AMgaryaustin
10/04/2021, 5:04 AMYogurtDrinker
10/04/2021, 8:06 AMsupabaseClient
at the _app.js
so every following page can use it right?Mihai Andrei
10/04/2021, 8:47 AMmagicbyt3
10/04/2021, 10:38 AMjavorszky
10/04/2021, 10:49 AMpublic.shadow_users
after an insert on auth.users
, however inserting a new user fails, because apparently the stored procedure that's triggered on auth.users
does not have permission to write to public.shadow_users
. Is this something I can fix on my end? is this a bug? Is this something that's working as intended and won't be fixed?
sql
create table users (
id uuid references auth.users on delete cascade,
email text unique not null,
name text
);
create or replace function shadow_users()
returns trigger
language plpgsql
as
$$
begin
insert into public.users (id, email) values (new.id, new.email);
return new;
end;
$$;
CREATE TRIGGER shadow_users_trigger
AFTER INSERT ON auth.users
FOR EACH ROW
EXECUTE FUNCTION shadow_users();
silentworks
10/04/2021, 12:20 PMJaeden
10/04/2021, 2:20 PMsilentworks
10/04/2021, 2:22 PMJanR
10/04/2021, 3:07 PM