Mark Burggraf
Mark Burggraf
So is this fixed? I just tested in the hosted version of Supabase: ```sql CREATE OR REPLACE FUNCTION get_session_user() RETURNS text LANGUAGE plpgsql AS $$ BEGIN return session_user; END; $$;...
What's the current status of VFS support?
I figured I could hack it with: `onRecordAfterConfirmPasswordResetRequest` but that doesn't seem to be firing when I click to reset my password, or maybe I'm misunderstanding that hook?
I just never see that trigger firing for some reason.
Never mind, my mistake. Environment isn't set up right.
Yep, that works. Hooks rock.
Yes, I have inserted hundreds of thousands of records. You might just try batching them using the technique I wrote about here: [speeding-up-bulk-loading-in-postgresql](https://dev.to/supabase/speeding-up-bulk-loading-in-postgresql-41g5) Basically, use: `insert into table (f1, f2)...
There's no reason why large sql inserts would not work other than resource limitations on your browser. We're running a 32-bit Linux vm in the browser and then loading PostgreSQL...
This is incorrect. `session_user` should return `authenticator` if the call is being made from the javascript client (where the role can be either `anon` or `authenticated`. As it says in...
However, this block seems backward (and is indeed a bug!) Can you verify this and make sure I'm correct here and that this is indeed wrong? ```sql IF coalesce((current_setting('request.jwt.claims', true)::jsonb)->'app_metadata'->'claims_admin',...