I realize this is from a few months back, but did you find a solution to this?

How do i start a supabase realtime query with operators other than the eq. operator. Usually I query through:

supabase.client .from('$tableName:id=eq.$documentId')

. According to the walrus github other operators like gt. would be supported. But I always get an Unhandled Exception: relation "..." does not exist. Would be really nice if anyone could help 🙂

Hi all, I'm not great with databases and have a db design question. I have a table for tasks, and a table for sessions (in the frontend you can start a timer, and the session has a task id, start time, and stop time). I'd like to have a "total time spent" feature in my frontend, but I'm wondering how to calculate that from my database. Should I create a new property and update it each time the value changes, or is there a special query I can make that will calculate it without much overhead? I feel like the first approach is a bit hacky, but I'm scared that querying the database so many times just to get each tasks "total time spent" is a bit much. Any input/help would be appreciated!

Realtime operators

im getting this (sorry for the red box, thought i had the region selection selected

Hi, can someone help me here =) https://github.com/supabase/supabase/discussions/5461#discussion-3876574

Hi! With regards to service_role keys, is it safe to add it in Vercel's environment setting? Or it should be stored in another way to make sure it's protected? Thx 🙂

Im trying to hook up a supabase db to google's data studio but having some problems. Has anyone successfully done this? With SSL enabled, they want a client key and certificate along with the server certificate. I know the server certificate is available to download through the supabase db but any idea how to create or get a client key and client certificate?

I am using google oauth provider and getting this error

Error 400: redirect_uri_mismatch

edited with solution: in google cloud console add the url with /auth/v1/callback and it will be fixed

Hi, any hint in how to query based on a column that is a timestamp ?

llooks like this works. const { data, error } = await supabase .from('reminders_scheduled') .update({ flagBlockedBy: threadId }) .eq('flagBlockedBy', '') .lte('sendAt', 'now()')

is there any way to update with a limit(1)

?

Hey Bros I wanted to ask something In docs it's written that each project is provided with a dedicated database Does that mean supabase is a single tenant application??

Hi everyone. New to supabase and I have a question about users management with this tool. I have read that we cannot access the users in supabase for security reasons and some people duplicate the table to make some features work. My doubt is that I am planning to move a codebase to Supabase and wanted to manage the users with supabase but would love to have our custom built-in admin dashboard. This is being able to see all the users, edit them and or delete them (only from superadmin users in my website). From what I have read on the internet this is not possible? And all the management needs to be done on the Supabase UI dashboard? I am missing something here? Thanks!

Hello guys, I saw various topics on internet about the "issue" on integrate Supabase oauth on server logic, for example for APIs etc. To help people on that, I made a very simple middleware to handle it. https://github.com/WilliamFalci/supabase-oauth-server-side

does supabase storage have some kind of cache? i deleted a file and reuploaded one with the same name but its still returning the old file

Check if ur browser have it in cache

not using a browser; this is in a node script

Uhmm

await supabase.storage .from('templates') .update( name, fileContents, { contentType: mime.lookup('docx'), cacheControl: '0', upsert: true } )

whats the point of freezing a column?

js
let { data: requests, error } = await supabase.from('requests')
    .select(`
        *,
        status!requests_status_id_fkey (*)
    `)
    .order('created_at', { ascending: false })
    .neq('status.name', 'Archived')
    .eq('user_id', user_id)

So I'm using this query against the API currently. However, this is still returning requests which are 'archived'. I even tried doing status.id and doing

.neq(status.id, #)

and that still returned records with 'Archived'. Am I doing something wrong? I cant find anywhere in the documentation where to filter on relationships, it just appears not to work.

interesting enough, this returns a status relationship for records without "Archived", but not for those with 'Archived'

So what is "not" 'Archived'. Null does not count, it is ignored completely.

it's pretty simple.

requests

have a

status_id

. status table has 4 statuses, each with a unique name, one of them being Archived. There are others like 'Picked Up', 'Completed'. But this filter doesn't seem to do any filtering on requests itself, it instead filters the returned joined status.

i can filter on the client side if i need to, but that seems inefficient

looks like filtering on a relationship was just added to PostgREST in 9.0.0, so maybe the supabase-js client isn't caught up

Hi, I am running into a problem with the

GetPublicUrl()

method. What happens: 1. I uploaded an image to a bucket. 2. I displayed the image using getPublicUrl(), the correct image showed up. 3. I uploaded a new image (with upsert: true) with the same name, Succesful. 4. I tried to display the new image with getPublicUrl(), but it keeps returning the old image.. The image is updated when I check app.supabase.io, but when I request the public url from there, it gives me a supabase.in url instead of supabase.co. I tried several thing including cache control, but can't figure out why my app keeps displaying the old image. Anyone recognises this or knows what I am doing wrong? Thanks a lot! PS: I see a similar case was reported in this channel 3 hours ago by @User

Good evening all - I'm trying to use Supabase with Nuxt and I'm experiencing a weird error. I'm using the Nuxt

fetch

hook to retrieve data (my app is using SSR) and when I first navigate to a page I call

this.$supabase.auth.user()

from

fetch

and get the user info back but if I refresh the browser

null

is then returned, which is causing me a real headache... I can see the user info still in localStorage but I'm not sure why the call to get the user info fails after a reload?