-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Running LiveQuery with matchesQuery returns no results. #2946
Comments
So, I guess relation queries are not supported on subscribe/liveQuery? |
It seems that it's not supported yet. Do you want to try to add that support? |
I still don't speak fluent Parse, but I could give it a go. |
Awesome! Excited to see that one land! |
@danibjor I just stumbled over the same problem, how's your progress on supporting this feature? |
@dpoetzsch Not too good - need to find time to better understand everything that is involved, so I don't break anything.. |
So I investigated a bit today. I would guess that basically we would have to add a case in the switch statement in QueryTools.js, line 279 for Any ideas maybe on how to make this more efficient? |
The overhead is effectively significant. But that probably can be logged as a warning when subscribing to that kind of query. Moreover if the secondary table is improperly indexed. |
Also, you can use async/await to check the query match in that case, as babel will transpile to yield that should be supported in node 4.5 |
I'll give it a try with async/await and the additional required read.. |
Subscribe to RadioLocation instead, where the Radio ID is in an array of IDs. |
Closing due to lack of activity, please update to latest parse-server version and open a new issue if the issue persist. Also, for now, LiveQuery don't support complex queries that would require additional access to the database. |
Any plan to support parselivequery on parserelation? |
Would love to see that feature |
Wow, 4 years and they don't added requested feature. Nice. |
@FNPCMDs I will give this a crack, be mindful parse is a community based project that requires contributions from people who need features for their own projects. You’re welcome to submit a PR or join discussions on the community forum, but please be respectful. |
Issue Description
Running LiveQuery with matchesQuery returns no results - if the same Query is executed with find( .. ), results are returned.
Steps to reproduce
Running the query in Chrome console (chrome dev tools)
returns
So, the query returns expected results when .find() is executed - but no events when using LiveQuery. If I remove the innerQuery and filter on Radio.UpdatedAt, events are fired - so LiveQuery are working.
Expected Results
Events triggered when RadioLocation gets new items
Actual Outcome
No events gets triggered
Environment Setup
The text was updated successfully, but these errors were encountered: