Powershell link
Im trying to link my powershell to correctly deploy an private project im working on
when i run
supabase link --project-ref <my-project-id> it asks me for the database password, but i cannot type in there as it does...
process 75324 still waiting for AccessExclusiveLock on relation 28371 of database 5
I'm running into a locking issue again and could use some help. I tried to remove a column from a table using DBeaver, and the query just kept so I eventually canceled it. Then I checked the logs and saw the error in the title (plus the image).
This isn’t the first time I’ve hit this. It also happened when I tried to add RLS policies a while back. Previously, restarting the project fixed it, so I didn't dig into it much, but now it’s happening again and I’m not sure what’s causing it.
It’s just me on the DB as far as I know, so I’m kinda lost on what’s holding that lock. Any idea what might be going on?...
cant log in
I'm a long time user of Supabase. I'm trying to log in and I keep getting this error that I've never ran into. I'll attach the screenshot. it just logs in and then freezes and shows this
Multi-Tenancy allowed with 1 Acconut (1Project)? || Best Practice for a Multi-Tenant SaaS App
Hello everyone!
I'm building a SaaS invoicing application that will serve multiple, distinct companies (e.g., starting with 30 clients).
My plan is to use a single Supabase project for all of them. I intend to implement multi-tenancy by adding a tenant_id (or customer_id) column to every relevant table (like invoices, customers, etc.) and then use Row-Level Security (RLS) policies to ensure that users from one company can only see, edit, and create data associated with their own tenant_id....
Hey there!
I've been using Supabase for an enterprise level project and I've enjoyed the convinience that it provides. To continue using it I need some clarity on a few things -
1. How does Supabse use Cookies in a nextJS environment? I've been trying to check the "HttpOnly" attribute on the cookies (security concerns) but according to the docs, Supbase's client library needs constant access to these cookies for refreshing the auth tokens in the cookies. How do we manage this? The cookies become vulnerable to XSS attacks if this attribute is not on.
2. How do we decrease the expiry time on tokens using the dashborad? Each time I go to the dedicated option I'm redirected to the API settings page, is this a bug? Please clarify this ASAP? 😁
Here are the reproduction steps - Project settings -> Authentication -> Access token expiry -> and then i reach the API settings tab, why?...
Unable to Insert Data into Supabase users Table Due to Row Level Security (RLS)
I am experiencing an issue where I cannot insert data into the users table in my Supabase database. The operation fails due to Row Level Security (RLS) being enabled. Although the table structure is correct and the insert query is valid, Supabase returns a permission error indicating that the insert operation is not allowed under the current RLS policy. This is preventing me from creating or registering new data entry in the table through my application.
I suspect that no insert policy has been defined for the users table, or that the existing policy does not allow inserts for the current session role (typically anon or authenticated). I need to correctly define and apply an RLS policy that securely permits user insertion while maintaining proper access control which I think have dont but it doesnot allow entering new data into the table.
The given are my table info and the policy that i have created....
