arcavid
05/27/2022, 1:40 AMNeedle
05/27/2022, 1:40 AMgaryaustin
05/27/2022, 1:51 AMNeedle
05/27/2022, 1:51 AMarcavid
05/27/2022, 1:56 AMbrandymarsh
05/27/2022, 1:56 AMtrue
.
but, there are cases where you would not want users to be able to update every row of the table, so being more specific can help further give some guidance here, e.g. if a user could only update rows that contain a column user_id
that matches their id
, you could do auth.uid() = user_id
, assuming you're calling the function with an authenticated userarcavid
05/27/2022, 1:57 AMarcavid
05/27/2022, 1:57 AMarcavid
05/27/2022, 1:57 AMarcavid
05/27/2022, 1:58 AMgaryaustin
05/27/2022, 1:59 AMarcavid
05/27/2022, 1:59 AMgaryaustin
05/27/2022, 2:00 AMarcavid
05/27/2022, 2:01 AMgaryaustin
05/27/2022, 2:02 AMgaryaustin
05/27/2022, 2:02 AMarcavid
05/27/2022, 2:03 AMarcavid
05/27/2022, 2:20 AMsql
set search_path = public
is this needed?arcavid
05/27/2022, 2:20 AMgaryaustin
05/27/2022, 2:21 AMarcavid
05/27/2022, 2:23 AMsql
create OR REPLACE function comment_counter() returns trigger
LANGUAGE plpgsql
security definer
SET search_path = public
as $$
begin
update public.link
set comment_count = comment_count + 1
where id = new.link_id;
return new;
end
$$;
garyaustin
05/27/2022, 2:26 AMarcavid
05/27/2022, 2:27 AMarcavid
05/27/2022, 2:27 AMarcavid
05/27/2022, 2:28 AMgaryaustin
05/27/2022, 2:28 AMarcavid
05/27/2022, 2:30 AMgaryaustin
05/27/2022, 2:31 AMarcavid
05/27/2022, 8:20 AMgaryaustin
05/27/2022, 12:39 PM