But there is no guarantee there will be a

public.users

table so idk how that would work. Probably better as your own custom function

Functions can include logic that could check for the presence of

public.users

and

user.auth_id

or whatever is needed and then do the right thing. Right?

Access user personal info in policy documents

I think it would be great if we get autocomplete on sql function definitions and also logging especially with function calls

+1

support lua/luau

custom auth is necessary

can you expand on that?

feature request: option to be able use postgraphile (with or possibly without postgrest) to generate a graphql api using the same tables and RLS policies

feature request #2: "serverless" "worker" functions, it would be great to be able to eg run a nodejs function that does react SSR (via nextjs or whatever) on my supabase instance, to cut down on the latency between server rendering and data fetching

yeah the button to downgrade your service should be red for danger.

just like anon login, more some situation like if company have their own user system, their use their own issued token as login method?Or use username+password?

also, maybe you can use dashboard to generate new user, that will be good for those want invite base registration system

would be nice if we could multi select users here!

What action would you be looking to perform if you could multi select them?

mostly delete

Data connector for DOMO, Tableu, PowerBI, etc. That would be a huge market for Supabase.

Would allow BI dev teams to build out custom forms or apps that feed into their data visualization suite

> Data connector for DOMO, Tableu, PowerBI, etc. I think all of those support OData, which could come in the future(through PostgREST).

Can we add #swift to the list of #843999948717555735 channels?

QUICK, what do i build with supuabase im bored

This channel is for suggestions and ideas of how to improve Supabase itself, not for ideas for personal project.

Swift help channel

Heeey, would it be possible to somehow whitelist IPs that can access the PostgREST endpoint? I recently built https://workers.run and I am actually proxying all the user's requests through Cloudflare Workers, in order to inject some more data in-flight 💡 (specifically I am building the js bundle and adding it to the payload as another row column) Would be great if I could also protect the PostgREST endpoint this way - to say only Cloudflare IPs can access it, so I could set other rules/rate-limiting directly in my Cloudflare Zone 🙂

This is on the roadmap https://twitter.com/everConfusedGuy/status/1431612873919188996

Ohhh neat, thank you!!

https://github.com/supabase/supabase/issues/2979 Hey @User please look into this

✨ custom domains for storage instances ✨

I think you guys should show more attention towards native SDKs instead of just focusing on web and js.

You could have just stopped at the first comment, the tone of the second sounds a bit off