hi

Hey

Also loving Supabase,

Hop into #839993398554656831

Awesome, will do

Is it possible to get supabase storage to persist images in browser cache?

even though there is a cache-control header, status code for public resources (eg. ) is never 304

would it also be possible to persist signed URLs in browser cache as well? afaik, createSignedURL signs a token that is returned as a query parameter. maybe storage-api could cache signed urls by their etags, so signed urls don't change on every request. also, i don't think it makes much sense for createSignedURL to be a POST request since it doesn't change server state, and caching post requests isn't common.

storage caching bug

the only reason it might be POST is because sending a body with GET isn't part of the spec/supported

express-js usually lets you accept

body

in GETs but like I said, it's generally not supported by stuff

would like some help over here if anyone here has played around with supabase real time ->

I want to filter like this on a realtime subscription, is it possible and if yes, what's the correct syntax?:

column_a=eq.$userId OR column_b=eq.$userId

hello, is there a way to identify if a user is logging in via magic link?

check the user object, i remember seeing a metadata property with a provider key

yes there's a metadata property, but it specifies

provider: email

, which would be the same as someone that logs in via the usual email + password method

then your best bet is to probably update/insert a record on your auth table with a bool indicating it's a magic link user after the user gets redirected by clicking on the link. the key shouldn't be the same imo, so worth putting up an issue

alright, thank you!

Hi guys, anyone meets an error called “an invalid response was received from the upstream server“ while calling the signup function???

are you checking if column_a or column_b exists or are you checking if they have the userId? supabase doesn't do anything smart/fancy with with the table name you throw into

from()

so you would just follow the syntax of postgrest, so you wouldn't use OR as in the SQL operator, you'd use

or

but I don't quite get what you're trying to do

I am trying to filter if the userId exists in column_a or column_b, sorry for confusion

and why would you do this with a realtime sub?

to put it in a better way, is it possible for you to run that filter query before you create the sub?

It's necessary to filter both with a realtime subscription

my bad, i went down the rabbit hole and found out that while apparently

SupbaseQueryBuilder

extends

PostgrestQueryBuilder

, the table prop from

from()

is handed off to

SupabaseRealtimeClient

when calling

on()

. So the postgrest syntax is not valid

i couldn't find any syntax validation on the realtime-js lib so i guess the validation is done on the server-side and as far as i can see, you can't do most common db operations before making the subscription. afaik the only stuff that works rn is listening to changes on a table, or on certain rows

Thanks for your help, then I might use two subscriptions for now until something changes, even though i don't like this approach

you could instead listen to the table changes in general, and perform the filter query once the change has been streamed too tho

Can someone suggest a way. I'm using vanilla JS so i've imported the CDN JS file. In the bottom there is

<script src="https://cdn.jsdelivr.net/npm/@supabase/supabase-js"></script>
        <script src="index.js"></script>

So in my index.js i do something to test whether it's working

const { createClient } = supabase;

const supabase = createClient('MyLink', 'MyKey');

document.addEventListener("load", async() => {
    const {data, error} = await supabase.from("Course").select();
    console.log(data);
});