-
-
Notifications
You must be signed in to change notification settings - Fork 160
ParserError: Expected identifier at )
when using relation with no columns selected
#445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
2 tasks done
Labels
Comments
Thanks @vladshcherbin! This is a new feature from PostgREST v11 (using |
bnjmnt4n
added a commit
to bnjmnt4n/postgrest-js
that referenced
this issue
Nov 5, 2023
bnjmnt4n
added a commit
to bnjmnt4n/postgrest-js
that referenced
this issue
Nov 5, 2023
bnjmnt4n
added a commit
to bnjmnt4n/postgrest-js
that referenced
this issue
Feb 8, 2024
bnjmnt4n
added a commit
to bnjmnt4n/postgrest-js
that referenced
this issue
Feb 23, 2024
bnjmnt4n
added a commit
to bnjmnt4n/postgrest-js
that referenced
this issue
Feb 29, 2024
steve-chavez
pushed a commit
that referenced
this issue
Feb 29, 2024
🎉 This issue has been resolved in version 1.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Describe the bug
When using anti-join and not selecting any columns,
ParserError
is shown.Query:
Error:
The query is working and returns correct results, only typescript is showing this error with no types as a result. After adding any field (for example
car_images(id)
) the error disappears and typings are correct.Article with similar example (
nominations
relation): https://supabase.com/blog/postgrest-11-prerelease#anti-joinsExpected behavior
No typescript typings error, return type should not have this relation.
Screenshots
System information
The text was updated successfully, but these errors were encountered: