Is there any PR which fixes those? I recently updated supabase-js version and generated new types and got similar issue, some database fields are not recognized anymore. I cant pinpoint the exact moment it stated to break tho.

Edit: For me this solved it - #974

Same problem for me even when switching to 2.39.3

i got the same error

Same here!

same here...

still an issue

Same here. Weirdly, this works...

supabase
  .from('selection_assets')
  .select(
    `
    id,
    comment,
    order,
    created_at,
    asset: assets (
      id,
      name,
      is_listed
    )
  `,
  )
  .eq('selection_id', selectionId)
  .single();

and this doesn't...

supabase
  .from('selections')
  .select(
    `
    *,
      client: client_id(id)
    `,
  )
  .eq('id', selectionId)
  .single();

still an issue

Got the issue too

Same issue

Any solution?

I have the feeling it depends on in which direction or on which side the relation is defined. Still need to verify this.

@ohrrkan As mentioned in the documentation here:
https://supabase.com/docs/reference/javascript/select
(example for 'Query referenced tables through a join table')

We can infer types by doing this:

// To infer types, use the name of the table (in this case `users`) and
// the name of the foreign key constraint.
const { data, error } = await supabase
  .from('messages')
  .select(`
    content,
    from:users!messages_sender_id_fkey(name),
    to:users!messages_receiver_id_fkey(name)
  `)

Worked for me.

this works for me

  const { data, error } = await db
    .from("posts")
    .select(
      `
      id,
      content,
      user:users(
        id,
        full_name,
        handler,
        avatar
      )
      `
    )

user is the column name in posts
users is the name of foreign table.

A fix has been released in supabase-js v2.46.0. I'm closing this issue, but feel free to reopen if you encounter any further errors.

I am using v2.46.1, and I have same issue here

Same issue

@KouroshBhl @Gabriel-Volpini

We had to revert the fix in 2.46.1 as we had some unexpected breaking changes due to the type rework.
However, we did released a new version as a "release candidate", and we are currently collecting feedback about it: https://github.com/orgs/supabase/discussions/30324

Please give 2.46.2-rc.3 a try, and don't hesitate to report back any remaining error with the debugging informations mentioned in the discussion. In the meantime I reopen this issue and will be closing it when this release candidate land on the main release channel (which should happen in December).

Happy to announce that we just released v2.47.8 that include the typing inference rework which should fix this issue.