Support email

Hey! Does realtime support replaying events in case of reconnection? I Have a background process that updates large amounts of data in database, and a realtime listener which listens to changes, and propagates them to a secondary storage. However, I found that if my listener (not the supabase/realtime process, but a client using RealtimeClient JS api) crashes and is restarted, it misses all updates that occured when it wasn't running. Ideally, i'd like to maintain some position of the client in the realtime server, and ack each message, and maintain a window of messages in case a client reconnects and wants to replay the messages since its last position. I could even handle all the position logic on the client, as long as I could pass a timestamp, id, or whathever of the last seen data, and start replaying events since then. I used to work with CDC pipelines, and they were pretty heavy, used Kafka, etc. I'm trying to avoid all that complexity since I don't need scale, just a resilient way to get access to a log of database events.

Edit: Solved, I just have to pass str datetime. I am using supabase python client, how to manage datetime field? Passing datetime object to supabase.table().insert({"timestamp": datetimeObject }) returns following error:

TypeError: Object of type datetime is not JSON serializable

unfortunately the same for me. a few days ago a PR was published with a fix, but still not reviewed. https://github.com/supabase/postgres/pull/147

Can someone help me with querying the database? I have something weird going on and I don't know why

I have asked this question on Stackoverflow as well but I've received no answers

A nested query (a nested join in this case) refuses to give me the data because there are no relationships found, it says

Is it possible to use RLS without using the supabase client?

RLS is on the server-side. Or what are you asking exactly?

I want to make use of supabases helper functions like auth.uid() but without using supabases auth.

I've only just started using Supabase so I'm not that familiar with its components. But isn't auth.uid() an integral part of the authentication with supabase?

yeh it is but im not sure if i could customize it to use my current auth setup which is with firebase.

Aha, I have some similar problems. I haven't really worked on it yet but only theorised about combining both services

You could save the uid from Supabase with a

SupabaseUids

collection on Firebase and similarly you could store the uid from Firebase inside a

FirebaseUids

table?

I managed to fix it, most of the container got arm builds from Supabase recently so that fixed most of it, but Postgres didn’t and was configured to only build for ARM, I just built that myself and everything worked like a charm!

RLS without supabase.js

is it possible to use other columns from auth.user to create policies, just like how we use the default helper functions like auth.uid()|role() ?

for instance if i want to use the raw_user_metadata column when creating a policy, will this be possible?

I want to allow only whitelisted users to sign up with an email and password, what's the best way to do this?

that's oddly contradicting, isn't it?

Ah I mean that I want my email auth to be "invite only"

users will still need to create their password before using their account of course

Can I use backblaze storage along with hosted version of supabase

Anyone has an idea on how to make this?

Storage providers

Querying multiple or nested objects

I'm getting an error when running supabase via docker on a new Ubuntu 20 server.

supabase-rest | 21/Feb/2022:19:50:29 +0000: {"details":"could not translate host name \"l@db\" to address: Name does not resolve\n","code":"","message":"Database connection error. Retrying the connection."}

I have "enable email confirmations" disabled, and yet I still get a 400 Email not confirmed error when trying to sign in with an unconfirmed email

Hey, I'm trying to set up Supabase auth with Prisma. I've seen some threads in the channel for this, but none have any concrete replies. In addition I found a few threads on Prisma's repo with links on how this may be achieved, for example - https://github.com/prisma/prisma/issues/5128. I tried this out,

set

a custom variable

app.current_user_role

on a table which will allow Select only if

app.current_user_role

is

admin

But when I run this via Prisma, it returns all the rows, irrespective of this value. I wanted to know if this is a good idea at all, or if getting Prisma to work with Supabase auth is still tricky and best not attempted right now? Any pointers in the right direction would be great, thanks!