Skip to content
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

Closed
felipeweb opened this issue Dec 9, 2016 · 3 comments
Closed

OR filter (where) #33

felipeweb opened this issue Dec 9, 2016 · 3 comments

Comments

@felipeweb
Copy link
Member

No description provided.

@avelino avelino added this to the 0.1 milestone Dec 29, 2016
@avelino avelino removed this from the 0.1 milestone Jan 16, 2017
@avelino
Copy link
Member

avelino commented Jan 16, 2017

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)

@avelino avelino closed this as completed Jan 16, 2017
avelino pushed a commit that referenced this issue Jul 16, 2020
avelino pushed a commit that referenced this issue Aug 21, 2020
The attribute of table name should be `name` instead of `table` based on what I read from the documentation and the examples.
@pastarace
Copy link

Hi any news on that with the 1.0.0 release? I know in PostgREST OR and complex filtering is available

Thanks

@avelino
Copy link
Member

avelino commented Sep 17, 2020

@pastarace we still don't support complex or operations, can you open a new issue for us to feature?

It's a resource that pREST needs to learn how to handle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants