Hi all... Does supabase expose (in the rest api or graphql) only the "public" schema or every schema I eventually create ?

Sorry for the noise... I read the answer to my question...

https://twitter.com/moein_tech/status/1482387851941711879 Please let me know if you are interested 😃

Can you move your data to self hosted easily ?

Hello everyone, I hope you have a great week. tl;dr Are there any plans or alternatives to the below project for Kotlin (Multiplatform) support? Full message I plan to use Supabase on a Kotlin Multiplaform project. There, I need Supabase for Kotlin and didn't find a complete stack like for JavaScript. So I started migrating the entire supabase-js stack (Client, PostgREST, GoTrue, Realtime, Storage) to Kotlin Mulitplatform. The project can be found here https://github.com/malliaridis/supabase-kt (it lacks of documentation and tests tho). 👀 Are there any alternatives known yet for Kotlin Multiplatform? Due to the lack of time I am not able to finish and keep up-to-date this project alone. I would like to know what your thoughts of this approach are. I would also appreciate any feedback or input from (Kotlin) developers. PS. I looked into the code of the existing kotlin projects and I liked the modularity. But I chose a simpler approach for start due to the extended scope of the project.

hey thr

now that i am back

i would like to know

why i was kicked from this server

I'm confused about the api key setup with Supabase

If the api key is available on the client, aren't basically all of my tables publicly exposed?

I can setup RLS to prevent updating them, but there's no way to prevent reading them?

ie: Since you can't query the users table, I can setup a function to copy a user to a

public.private-users-info

table when created, but won't that also be exposed publicly?

It's probably best to explain what you are trying to accomplish here, the docs outline ways of handling some of this stuff too so it might be worth reading through it a bit.

I'm thinking I could: make the

public.private-profiles

table not publicly readable and use a service role to access the value I need on the backend?

when using workers, is it fine to createClient on every call?

Anyone else having a problem when making RPC calls to the backend like this:

Also, related to previous ^^ I'm curious how the service role should be used. I'd like to avoid using triggers/functions in Supabase, preferring to keep everything in my app. Could I use a service role via a backend api route to do the work of a trigger/function instead?

Reason for getting kicked

@User Apologies for using this handle for unofficial Supabase notifications, but it seems important. If you receive a message from

@Kiwicopple#9153

, they are NOT me and you should report them. If you receive a message from anyone who claims to be on the Supabase team, please double-check who they are before responding. They should have the

@Team

role on the server as a side note, I'd never use

Kiwicopple

, only

kiwicopple

😛

ok

copple impersonation is a crime punishable to the highest extent of the law

Arent all my tables public

RLS to prevent create, read, update and delete

User info

Is it possible to use the supabase API to do a bulk insert, and do nothing if the row already exists? I see upsert, but that would update the row if it exists. What if I don't want to update it?

Or would upsert without any actual changes to the row be effectively the same as doing nothing from a usage/writing standpoint?

Why does email auth redirect use hash instead of query parameters? eg. "#access_token=..." instead of "?access_token=...". Hashes (#) aren't sent to the server so can't handle redirect via a server route and instead have to make a client roundtrip to read the hash and then send it to the server. Others have mentioned this before, I'm curious if there's an actual reason.

Seems like it comes from this line: https://github.com/netlify/gotrue/blob/master/api/external.go#L215. Any chance this can change?

Hey Lawrence! The Hash is part of the OAuth spec but this is landing soon: https://github.com/supabase/gotrue/issues/279