You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolving joins on Computed Relationships in types broke somewhere between v1.16.3 and v1.17.7, resulting in an error like: SelectQueryError<"could not find the relation between placement and hotel">.
When a computed relationship is defined with a name that does not match the table involved (eg. function is placements(hotel), whereas table is placement), the types only work with the table's name, rather than the function's name, which is the opposite of what the postgrest api expects.
Bug report
Describe the bug
Resolving joins on Computed Relationships in types broke somewhere between v1.16.3 and v1.17.7, resulting in an error like:
SelectQueryError<"could not find the relation between placement and hotel">
.To Reproduce
See
src/supabase.test-d.ts
in theworking
andbroken
branches of my repro repo: https://github.com/hmnd/postgrest-computed-rels-reproExpected behavior
Computed Relationship is resolved successfully.
The text was updated successfully, but these errors were encountered: