Skip to content

Can you include query/object cache in next release ? it is the must have feature in mobile #55

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

Closed
ghost opened this issue Jan 25, 2019 · 4 comments
Labels
state:duplicate Duplicate of already reported issue type:feature New feature or improvement of existing feature

Comments

@ghost
Copy link

ghost commented Jan 25, 2019

No description provided.

@ghost ghost changed the title Can you include query/object cache in next release ? it is the must have in mobile Can you include query/object cache in next release ? it is the must have feature in mobile Jan 25, 2019
@phillwiggins
Copy link
Member

Hey

We haven't got that just yet. We've not found a suitable NoSQL dB for Dart that is stable enough.

This will be added in the future.

@ghost
Copy link
Author

ghost commented Jan 25, 2019

Thanks , hope it comes soon .
hey , i fount that this line in livequery is causing issue for me
subscribeMessage['query']['className'] = className;

so , for quick fix i have just moved
subscribeMessage = {
"op": "subscribe",
"requestId": 1,
"query": {
"className": className,
"where": {},
}
};

to subscribe class in parse_livequery.dart

@cadaniel
Copy link

HIve might be a good option for a pure dart NoSQL.

If your able to point me in the right direction I'd be instrested in contributing.

@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:improvement labels Dec 6, 2021
@mbfakourii
Copy link
Member

The subject of caching the object and sending it after the availability of Parse is called saveEventually, which is discussed in this issue, otherwise you can use nosql to save.

@mbfakourii mbfakourii closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2023
@mtrezza mtrezza added the state:duplicate Duplicate of already reported issue label May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:duplicate Duplicate of already reported issue type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

4 participants