[Question] will there be a way for the SDK to manage and cache queries in the future?

if not does anybody know how a cache system should be structured, im assuming when i do the query calls i need to save the results by document id and whenever i query to check wether it has been called within a certain time limit?

TL;DR

Developers are asking if there will be a way for the SDK to manage and cache queries in the future. They discuss the issue with offline support and the difficulty of knowing what gets deleted or updated. One workaround suggested is saving things locally and creating a document to track updates. However, there's uncertainty about receiving changes through realtime and the feasibility of handling caching client-sided. It is recommended to check the provided link for more information. No definite solution is mentioned, but it is suggested that developers handle the caching system themselves by saving query results and checking if they have been called within a certain time limit.

Caching server-sided or client-sided?

Client sided ofcourse

Not sure, but I think it's better to make that be handled by the user instead of the SDK. However this is a bit similar to offline support. Currently there is a repo in beta for flutter Offline support, maybe it has what you want

Since basically offline support is pretty similar to caching client sided 😅

i know there is one for firebase but it does not support DocumentList types

Check this: https://github.com/appwrite/appwrite/discussions/5326

But from what I'm seeing it gets everything by default so it only uses cache when network isn't available

The "Issue" is that you don't/can't know if something got or not updated

well they could check these documents with realtime subscription?

I think not, since when something changes, the app could be in the background and not receive the changes through realtime

oh i see

A workaround I recommend is saving things locally and then creating a doc called updated, for example. That doc has an integer attribute (for example, 0). Once you create a new document, you increase that number by 1. Once the app is opened, you check if that value has increased respect the saved (if so, you update since there's a new document that has been added), and if it's the same, you don't need to get anything (so you use cached elements)