Comment by williamdclt 1 year ago What do you mean by this? What authz would you expect/like? 3 comments williamdclt Reply cryptonector 1 year ago I'd like to say that only some roles can NOTIFY to some channels. Similarly for alternatives to LISTEN/NOTIFY. williamdclt 1 year ago Right. It’s not something I’ve had to handle, I’ve always worked in environments where db clients are well behaved and under my control, what’s your use case out of interest? cryptonector 1 year ago Security in depth. If I have to give someone login access, I should be able to control what they do.
cryptonector 1 year ago I'd like to say that only some roles can NOTIFY to some channels. Similarly for alternatives to LISTEN/NOTIFY. williamdclt 1 year ago Right. It’s not something I’ve had to handle, I’ve always worked in environments where db clients are well behaved and under my control, what’s your use case out of interest? cryptonector 1 year ago Security in depth. If I have to give someone login access, I should be able to control what they do.
williamdclt 1 year ago Right. It’s not something I’ve had to handle, I’ve always worked in environments where db clients are well behaved and under my control, what’s your use case out of interest? cryptonector 1 year ago Security in depth. If I have to give someone login access, I should be able to control what they do.
cryptonector 1 year ago Security in depth. If I have to give someone login access, I should be able to control what they do.
I'd like to say that only some roles can NOTIFY to some channels. Similarly for alternatives to LISTEN/NOTIFY.
Right. It’s not something I’ve had to handle, I’ve always worked in environments where db clients are well behaved and under my control, what’s your use case out of interest?
Security in depth. If I have to give someone login access, I should be able to control what they do.