Sudently relation between tables "does not exist"

Bug report

Describe the bug

I Have the following query:

  id,
  user (
    first_name,
    last_name
  ),
  created_at,
  appointments:appointments.specialist (count),
  account (
    balance
  )

It was working since the 17 of september of 2021 until this morning, no changes were made to this code since that date. And the request is responding “column specialists.appointments does not exist”.

Here’s the CURL generated by the frontend:

curl '.../specialists?select=id%2Cuser%28first_name%2Clast_name%29%2Ccreated_at%2Cappointments%3Aappointments.specialist%28count%29%2Caccount%28balance%29&deleted=eq.false&offset=0&limit=5'

Using the supabase-js library:

  supabase
    .from('specialists')
    .select(
       `
          id,
          user (
            first_name,
            last_name
          ),
          created_at,
          appointments:appointments.specialist (count),
          account (
            balance
          )
       `).eq('deleted', false)

If this “appointments:appointments.specialist(count)” is eliminated the query works

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Create a table called “specialists” or whatever you want
2. Create a second table called “appointments” or whatever you want and add a releation between this table and the first one. It can be “specialist -> specialists.id”
3. Fetch the table “specialist” and join with "appointments.

Expected behavior

A success request as it was before

Screenshots

The curl request from insomnia:

The relation in “appointments”:

System information

• macOS and Windows
• chrome, firefox
• Version of supabase-js: ^1.22.4
• Version of Node.js: v14.17.5

[tavoohoh]

@steve-chavez it did work!! So the issue was related with the new version of postgrest.

Thank you

[steve-chavez]

@tavoohoh Can you change appointments.specialist to appointments!specialist? As in:

  supabase
    .from('specialists')
    .select(
       `
          id,
          user (
            first_name,
            last_name
          ),
          created_at,
          appointments:appointments!specialist(count),
          account (
            balance
          )
       `).eq('deleted', false)

Btw, if you only do appointments(count) now, this should show a more friendlier error message suggesting the above syntax.