3 ms·
I second that! Would like to see supabase since that’s what I’ve been using a lot recently and really liking!
by jonplackett 5y ago
I second that! Would like to see supabase since that’s what I’ve been using a lot recently and really liking!
- mastazi 5y agoI have a question, how do you manage the fact that Supabase is based on a relational db[1]? Do you just put all fields (except the primary key) in a JSON column[2]? Does it work well if you use it that way? We were investigating it as a way to escape Firebase's vendor lock-in but the fact that we would have to manage schema migrations was a bit of a deal breaker based on our use case. I'm also interested in hearing about any alternatives to Supabase that use a document-based nosql db. [1] https://supabase.io/database https://supabase.io/database [2] https://www.postgresql.org/docs/13/datatype-json.html https://www.postgresql.org/docs/13/datatype-json.html
- jonplackett 5y agoPersonably I kinda like the fact that it’s a relational DB. The stuff you gain by having users only allowed to do certain things based on certain fields using Policies makes life a lot easier and more relaxing.
- mastazi 5y agoFirestore can do that, a DB engine doesn't need to be relational to offer that feature. https://firebase.google.com/docs/firestore/security/get-started https://firebase.google.com/docs/firestore/security/get-star...