5
Exploring new approaches to queries
Source: appwrite/appwrite#7197 · opened by @abnegate
We've been brainstorming on enhancing our query capabilities in Appwrite, particularly around ways we can support nested queries. As a result, we're considering some significant changes to our query serialization process and would love your input. This is an important decision, and we want to ensure all voices are heard. To allow nested queries, our idea is for the SDK code to look something like this: Where the queries nested inside the Query.or parameter will be grouped with an OR operator instead of the default AND. Current approach Our SDK methods like Query.startsWith('name', 'jake') return serialized strings ("startsWith(\"name\", \"jake\")"), which the API then deserializes back into Query objects. This has served us well, especially for straightforward queries. Proposed change However, with the introduction of nested queries, the complexity escalates. Consider the string output for a nested query usi…
No pledges yet. Be the first to back this.
Comments
Similar requests
Syntax for filtering documents
4 votes · 0 comments
Proposal: Appwrite Payments - Discovery Thread
3 votes · 0 comments
Serverless / Decentralized Appwrite; Specifically, a low-latency Primary Database Cluster or Blockchain serving distinct Appwrite installations and Frontends
1 vote · 0 comments
🚀 Enhancement: Add `Query.deselect` to Queries
0 votes · 0 comments
🚀 Feature: caching queries
4 votes · 0 comments
No comments yet.