New !inner join not working: "Could not find a relationship between trips and bookings in the schema cache"

Bug report

Describe the bug

I follow the syntax explained here: https://postgrest.org/en/v9.0/api.html#embedding-with-top-level-filtering

I am attempting to utilize the new inner join functionality. I attempt to perform a simple query. If I leave out “!inner” it works well, however, with “!inner”, I get an error:

{
    "hint": "If a new foreign key between these entities was created in the database, try reloading the schema cache.",
    "message": "Could not find a relationship between trips and bookings in the schema cache"
}

Example:

• Works = https://__.supabase.co/rest/v1/trips?select=bookings(id)
• Does not works = https://__.supabase.co/rest/v1/trips?select=bookings!inner(id)

To Reproduce

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

• Try similar queries as above

Expected behavior

I would expect, when not giving any filters to the query, to get the exact same response as if not including “!inner” in the query.

System information

• Happens both using the Javascript SDK and through direct REST calls in Postman

Additional context

• I have tried with multiple different relations in our setup. All of them behave the same.
• I have attempted to restart our Supabase server in the cloud dashboard but that made zero difference.

[steve-chavez]

@mbalslow Yes, that’s intended behavior - does an INNER JOIN under the hood - it excludes top-level rows without an explicit filter(actually it contains an implicit filter, the ON clause of the INNER JOIN).

Maybe this is on purpose but it should be clearly clarified in the documentation

True. Actually on the PostgREST side we are thinking of adding an alternative way to specify this operation, which would enable doing:

GET /countries?select=name,cities(name)&cities=exists.true

Or through postgrest-js:

const { data, error } = await supabase
  .from('countries')
  .select(`
    *,
    cities (*)
  `)
  .exists('cities', true)

I think that would make the filtering more explicit.

[mbalslow]

@steve-chavez I can confirm that it now works so it was simply a matter of time until the instance was upgraded