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
When searching an attribute in multiple columns, we need to use multiple queries because by default, appwrite queries are defined with a AND.
🎤 Pitch
In my use-cases, I have a collection "books":
Authors : String[]
Illustrators : String[]
If I want to search every books where creator "Timoleon" ($id = creator1) participate, I can't use :
Query.equal("Authors ", ["creator1"]), Query.equal("Illustrators ", ["creator1"])
because it will not return result where Timoleon was only illustrator or only author.
I will have to run two queries :
Query.equal("Authors ", ["creator1"])
Query.equal("Illustrators ", ["creator1"])
and remove all duplicates.
If Timoleon appear in 10 books, it's not a problem. But if request returns thousands of results, we can't use the pagination functionnalities (because we can't remove duplicates if we don't have all the results)
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
When searching an attribute in multiple columns, we need to use multiple queries because by default, appwrite queries are defined with a AND.
🎤 Pitch
In my use-cases, I have a collection "books":
If I want to search every books where creator "Timoleon" ($id = creator1) participate, I can't use :
Query.equal("Authors ", ["creator1"]), Query.equal("Illustrators ", ["creator1"])
because it will not return result where Timoleon was only illustrator or only author.
I will have to run two queries :
and remove all duplicates.
If Timoleon appear in 10 books, it's not a problem. But if request returns thousands of results, we can't use the pagination functionnalities (because we can't remove duplicates if we don't have all the results)
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: