TLooks correct to me
DThank you. Sanity check 
DDo you know by chance how I can expand this on the INSERTS side where a user can't have a request that matches an existing one?
DEssentially, if the sender_id and receiver_id are a match to an existing pair it means you already sent that request. How can I write a policy that rejects the 2nd insert
DOops, just thought of a solution. I can create a function that returns a bool if exists on this table and use that in my policy. Sorry to bug you
GThe proper way is to make both a joint unique constraint.
https://stackoverflow.com/questions/14221775/in-postgresql-force-unique-on-combination-of-two-columns
https://stackoverflow.com/questions/14221775/in-postgresql-force-unique-on-combination-of-two-columns
Stack Overflow
I would like to set up a table in PostgreSQL such that two columns together must be unique. There can be multiple values of either value, so long as there are not two that share both.
For instanc...
For instanc...
DAh okay, so I have something similar right now. A friend_requests table where users can post requests to. The user can choose to accept or decline which will trigger a function that if it's accept inserts into the friendships table a new row. If rejected it's just deleted.
