Export DB

RLS with role

Ok, found the issue. For whoever might face it. Supabase in order to insert, needs to also have a select permission to the Policy. Otherwise it wont work. If u dont want to add a select policy, simply add this to your insert statement insert(data, { returning: 'minimal' })

And fixes the error and u can properly insert data

posting IDs to a webhook

Transaction insert

hey there, newbie here. i'm trying to link the auth.users table to my main table. does anyone know if this is possible?

Any suggestion on this?

try nginx reverse proxy

Hello. I am trying to make use of

file_fdw

with a .csv file located in

supabase-storage

. I installed the extension, created the server reference and it shows up in my db. When I try to access the table, postgres says that it cannot open the file.

I'm not 100% sure how storage is networked in relation to the postgres instance. Should I be used a URL for my filename, a relative path for my filename, or something different (e.g. an SFTP path or S3-type path...)?

option 1:

'mybucket/myfolder/myfile.csv'

(not working) option 2:

'https://myproject.supabase.in/storage/v1/object/sign/mybucket/myfolder/myfile.csv?token=mytoken'

(no luck but auth requirements not clear)`

i wrote a workaround for this problem here: https://github.com/supabase/supabase/issues/2797

Hey! Is there a way to implement an array of Foreign keys?

I got an error if I check "Define as array" and add a Foreign key relation

Forget it, I'm using an intermediate table😆

Does anyone know if there is a way to change the emails that are sent when authenticating? I would love for the emails to be from our domain with our own custom designs.

Has anyone gotten this error when connecting to supabase db?

Error querying the database: db error: ERROR: prepared statement "s0" already exists
   0: sql_migration_connector::flavour::postgres::ensure_connection_validity

Are you connecting to pgbouncer? That error can come from an ORM(or any client) that uses prepared statements and connects to pgbouncer(which is in transaction pooling mode by default, prepared statements don't work here). Maybe try disabling prepared statements on your client. Or also, try changing pgbouncer "Pool Mode" to "Session".

@User thanks for getting back to me. I am using keystone which uses prisma. As far as I can tell prisma does use pgbouncer but when I get my really long error message it seems to indicate that pgbouncer is off. So ultimately, because it is abstracted away from me I cannot really tell if I am or am not using it. I will reach out to the keystone team and see if they have any similar issues. Another question, if I am having issues with Docker, would that also affect this? I am not sure how the two would work together but I know that I have been having docker issues. Just curious if this might also be contributing. Thanks @User

Hi this can be done using foreign keys. Check out the starters in the SQL section of the dashboard to see how it's done

Thank you!

Should the

postgres

user have rights on the

auth

schema? I have project where that is not the case. When I create a new project the user seems to be created WITH the rights.

so this would work linking the auth.users table that supabase provides with a users table that i've created with seperate data, correct? becuase i keep trying to link them and it doesn't seem to want to work

Yes it should work

Are you doing that through the interface or writing an sql schema?

If it's a schema it's easier to help you

@Mike92988 https://supabase.io/docs/guides/auth/managing-user-data