https://supabase.com/ logo
Join Discord
Powered by
# help
  • s
    If you want to make use of an updatedAt data point, yes
  • s
    updatedAt timestamp with time zone default timezone('utc'::text, now()) not null
  • w
    i updated my columns in the comment. I have 
    updatedAt
    but not 
    updatedat
  • s
    change your query to look for 
    updatedAt
    instead of 
    updatedat
  • j
    Helping is fun 😄
  • w
    where do i do that? i use the js-client all the time for crud ops. Just tried the ui to check if i'd get the same response
  • s
    Share the query you are running that results in that error
  • w
    I don't run any sql query per say. Only using js-client methods. Here's how i do it:
    Copy code
    ts
async updateUserAccount(user: Partial<User>, id: string) {
        try {
            const { error: supaError } = await supabase
                .from<User>("users")
                .update(user, {
                    returning: "minimal",
                })
                .match({ id });

            if (supaError) {
                throw supaError;
            }

            return true;
        } catch (error) {
            captureException(error, {
                tags: {
                    from: "[Database.createUserAccount]",
                    description: error.message,
                },
            });
            throw error;
        }
    }
  • s
    What's in the 
    user
    you are passing to 
    updateUserAccount/2
    ?
  • w
    type definitions for https://discord.com/channels/839993398554656828/843999948717555735/884240481800822784 . Currently, i'm calling updating the table with the following data: 
    await updateUserAccount({paystackSubaccountId: "ACCT_XXXXXX"}, "some-valid-uuid-for-user")
  • s
    That's what the table is expecting, I want to see what you are actually sending in your code
  • s
    So you pass it an object with only 
    paystackSubaccountId
  • w
    for now, only 
    paystackSubaccountId
    .
  • s
    When you added the 
    updatedAt
    column, how did you do that?
  • s
    Maybe below is trying to hit updatedat 🤔
    Copy code
    javascript
.update(user, {
  returning: "minimal",
})
  • w
    I used the dashboard(old ui)
  • w
    I don't think that's the issue because i face the same issue when i update 
    paystackSubaccountId
    from the dashboard
  • s
    That would be performing a similar query, just with a pretty front-end
  • s
    updating the record is trying to update a column that doesn't exist
  • s
    as a hacky check, rename the 
    updatedAt
    column to 
    updatedat
    and see if the error is the same
  • w
    I think i found the issue. It might be a bug from supabase. I replaced 
    updatedAt
    to 
    updatedat
    then changed value of 
    paystackSubaccountId
    and it was saved without any issue
  • p
    Anyone have issues with error 
    JWTIssuedAtFuture
    when creating JWTs? Basically I have a Firebase Function that issues a JWT for my users so they can query my Supabase DB. I am running my function locally on my machine in WSL. Apparently WSL has an issue with clock drift. Is it maybe possible to disable that expiry check in Supabase? I am using a test project so dont care about this stuff (only in prod)
  • p
    [for now I have turned off setting a creation date only in development]
  • m
    Hey there, I am using RLS and have it enabled all over. However, when I got no session, it returns all data. This shouldn't be happening, or should it? As soon as I am logged in, I only see data that is applying the RLS. I am USING 
    (uid() = user_id)
    + WITH CHECK 
    (role() = 'authenticated':: text)
    .
  • j
    try removing the 
    WITH CHECK
    ?
  • p
    I am at a place where I absolutely love RLS but somehow I'm also afraid I fuck it up, is there a tool or something to visualize all policies or right test for them or anything? what is the best practice here?
  • m
    Tried that, same result… I tried moving it as AND condition into the USING check which also does not work…
  • s
    This should probably be stated somewhere in the supabase docs, but don't use any other case than lowercase and underscores in table, column, function, view names. So instead of 
    updatedAt
    use 
    updated_at
    .
  • a
    Hey, i keep getting more and more failed requests to supabase, is there anything i can do to fix this? (I had a few errors daily before but the last 10hours i have gotten way more)
    Copy code
    FetchError: request to SUPABSEURL failed, reason: getaddrinfo ENOTFOUND URL
0|server  |     at ClientRequest.<anonymous> (/root/games/node_modules/cross-fetch/node_modules/node-fetch/lib/index.js:1461:11)
0|server  |     at ClientRequest.emit (node:events:394:28)
0|server  |     at TLSSocket.socketErrorListener (node:_http_client:447:9)
0|server  |     at TLSSocket.emit (node:events:394:28)
0|server  |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|server  |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|server  |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|server  |   type: 'system',
0|server  |   errno: 'ENOTFOUND',
0|server  |   code: 'ENOTFOUND'
0|server  | }
  • t
    Would be cool. :p Tell me if you find something haha.
1...757677...316Latest