-
-
Notifications
You must be signed in to change notification settings - Fork 279
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
OR filter (where) #33
Comments
After brainstorm we have come to the conclusion that we won't be able to implement without losing the REST feature. To make queries with OR (or where more complex) we recommend using VIEWS (within the database) or #70 (like view the level of application) |
The attribute of table name should be `name` instead of `table` based on what I read from the documentation and the examples.
Hi any news on that with the 1.0.0 release? I know in PostgREST OR and complex filtering is available Thanks |
@pastarace we still don't support It's a resource that pREST needs to learn how to handle |
No description provided.
The text was updated successfully, but these errors were encountered: