> No easy work around. Either have to generate own unique ID at client so you know it, (something like uid and time) or without thinking about it too much use an rpc function for the insert and then return your value, or do the rest of your operation on the other table at the same time in the function. Warning, late for me and just throwing out ideas to think about. > > - @User Actually on that note. Is there a way to know who the current executing user is while in SQL? e.g. I had a similar idea and put a

created_by_id

on the

collection

and then created the record on the join table based on the

created_by_id

which seems kinda hacky, but it works. Wondering if there's another way to get the user than saving it and reading it

create or replace function public.handle_new_collection() 
returns trigger as $$
begin
  insert into public.user_collections (collection_id, user_id)
  values (
    new.id,
    new.created_by_id
  );

  return new;
end;
$$ language plpgsql security definer;

-- Only needed once to create the trigger
create trigger on_public_collection_created
  after insert on public.collections
  for each row execute procedure public.handle_new_collection();