passing

undefined

for a value of an object to be upserted doesn't seem to translate to upserting as NULL (as you might expect?) instead it doesn't bother trying to use that key value pair and so i was getting the

All object keys must match

error

2lazy to write a github issue but hopefully this helps someone if they're searching discord

any suggestions on how to convert a date to milliseconds in an sql query on supabase?

To convert from Unix timestamp to datetime:

SELECT to_timestamp(<epoch time>);

To convert from datetime to Unix timestamp in ms:

SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '<date time>')

(Search for 'epoch' on this page for more details and examples: https://www.postgresql.org/docs/9.2/functions-datetime.html) Side note: Anything regarding SQL should go in the #869405720934744086 channel instead

how would one to many work? If i want to get a storypost along with its comments

Selecting related tables

#869406062036529193 Hey Guys, how to imlement upload and get image?

How to upload and get image

Any reason why it says Can't perform a React state update on an unmounted component for this.

useEffect(() => {
    const fetchJobs = async () => {
      setLoading(true);
      setErrorMessage(false);
      try {
        const { data, error } = await supabase.from("jobs");

        if (error) throw error;
        setJobs(data);
      } catch (error) {
        setJobs(null);
        setErrorMessage(true);
      } finally {
        setLoading(false);
      }
    };
    fetchJobs();
    // return () => fetchJobs();
  }, []);

Maybe missing

.select('*')

?

oh i still have the select but same error

React state update on unmounted component

In my NextJS app, I want a "Request to Chat" button. To do this, I already have the users id, but not their email address. I currently have it setup to query for their email and then send an email to that address via SendGrid.

But, this involves passing the email address through the client.

Anyone think of a way I could use a next api route to send an email without passing the email through the client?

Getting an error when trying to update a row with the library: "invalid input syntax for type bytea" not sure what that means though

Say, pals, what's the best practice right now doing client-side route protection, given that Auth.useUser() initially returns identical values for both the logged-in and logged-out case?

I've found about 1,000 people complaining that

supabase.auth.user()

doesn't return a promise, across stackexchange, github, reddit, and this discord. It's totally unintuitive, and it makes it massive headache to implement auth flows that should be trivial. Doesn't look like Supabase has plans to change it, though. Anyone got a favorite solution?

Access to Auth.user()

testing out Supabase auth and found something odd, wondering if somebody could enlighten me. if I call supabase.auth.signUp with an existing email address, I get an object full of user data including:

id

,

aud:authenticated

,

role:authenticated

, the email address,

email_confirmed_ad

,

phone

, and other bits of data. is that normal? doesn't that give anyone ability to see 1) who's registered in my app, 2) their phone numbers, 3) their last login date, and who knows what else? I would expect to get an error "email already registered" like in firebase maybe?

Great find, @User - I recommend you contacted security@supabase.io ASAP (more info about reporting security issues to the Supabase team: https://github.com/supabase/supabase/security/policy)

btw, it sounds to me that Firebase's behavior is also NOT ideal, because it still leaks info about whether a user is registered or not...

haha nice, this is something I found out just yesterday and I was weirded out by it. supabase doesn't throw any error if a user with a particular email already exists, but i kinda remember it throwing an error some time back

so it could just be the fact that some time back someone messed up, because for example the email confirmations aren't sent, the auth.users row for the user isn't updated

true but at least saying an email is already taken is pretty common practice

So i guess they did make the change recently

what’s weird about this behavior is that i don’t even know what to tell such a user. if a legitimate user is trying to create an account with an existing email, it seems impossible to differentiate supabase.auth.signUp’s response for 1) a user who successfully signed up but needs to confirm their email, or 2) a user who forgot they already had an account and needs to actually sign in

oh nice i’ll look into that issue

apparently it's just fake data that's returned when you call auth.signUp()