https://www.postgresql.org/docs/current/sql-grant.html

GRANT ALL ON <view name> TO service_role

btw, for RLS to work, you dont have to set

authenticated

as the owner of the view

RLS should work for non-table owners as well

It doesn't seem to. Any user could look at RLS-restricted records by using the view. When I changed the owner to

authenticated

then it started being restricted

IIRC it is because views are executed from the perspective of the user who created them

ah ok then i probably recalled wrongly

@User RLS is executed at the level of the user who implments it. Can you show an exmaple?

Also once you turn on RLS for a table, every action is now restricted until you specifically clarify the policy

I have a view that mashes together my public.users and the auth.users. RLS works from the public.users table on it. I may be crazy

hi, say i have a *Post and Comment tables, and l need each Post record to contain a list of its comments, how can i do that?

in the comment table put a foreign key to the post

I asked this in the javascript channel but it's more appropriate here. I want to auto calculate a datetime 30 days in the future and put it in

valid_until

. Below does not work.

ts
await supabase
  .from('posts')
  .update({ valid_until: `now() + interval '30 day'` })
  .eq('id', postId);

However using just

.update({ valid_until: 'now()'})

works (but doesn't achieve my goal)

I don't think you can pass in arbitrary text which will be treated as SQL expressions. I think the easiest workaround is to do this client side, or you can create a function which you invoke via

supabase.rpc

in which you can then use whatever SQL expressions you need

Cheers, a function is probably the go then 👍

Fwiw it’s not arbitrary text, that’s psql datetime operators but maybe they aren’t considered valid in an update statement?

Haven't dug deeply into it, but I suspect postgrest treats most inputs as text to avoid possible sql injection operations

Stored procedure

Hey! guys is there a way to convert an sql table to the supabase ways of doing it?

How can I turn the above code into supabase schema and then use policy and what a view

SQL in supabase

If I run the following via the SQL editor it always results in a new version of

my_func

(which means I have duplicates). How do I force the

replace

part to work?

create or replace function my_func(...

it probably means your input/output arguments across the old and new versions are different, resulting in 2 separate functions with the same name from the docs: https://www.postgresql.org/docs/current/sql-createfunction.html > However, functions and procedures of different argument types can share a name (this is called overloading). > > To replace the current definition of an existing function, use CREATE OR REPLACE FUNCTION. It is not possible to change the name or argument types of a function this way (if you tried, you would actually be creating a new, distinct function). Also, CREATE OR REPLACE FUNCTION will not let you change the return type of an existing function. To do that, you must drop and recreate the function.

Yes the input arguments are changing

So I should delete the old one before running my query?

yes, if you dont want to have multiple functions with the same name

Fair enough

Thanks!

Any chance supabase is going to update to 14?

Postgres 14 upgrade