-
-
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
Live query with include won't work #1686
Comments
My understanding is that 'include' is not supported in LiveQuery yet. You will get back to the pointer information and can perform a fetch there or implement some local caching so you don't have to call the server to resolve those related records. |
Currently I just use the pointer id the get the user I'm looking for via another query, so I didn't understand you perfectly, should I be able to use include or its not implemented yet(with LiveQuery)? |
It's not implemented using Live Query. The way you are doing it is correct. My last comment was just a suggestion that you keep user records in a local cache so you don't always have to immediately fetch from the server every time. |
Hi to all! Any update or support about |
Any news about that? |
I clearly see that there is interest in this topic. Is there a particular reason this won't work? |
Thanks for opening this issue!
|
This seems like a bit of random limitation that should not be there. Are there any plans to address this issue? |
Does anyone want to open a PR? |
I have a table, one of the table fields points to the users table, here is my code:
Within the parse server
index.js
I set:I also tried another table, other than users table, doesn't work either.
This is the response(if it helps):
Honestly, I'm not sure if it's a bug but I was trying to find out if it's even possibly to use include with live query and didn't find anything like that in the docs, but the docs suggest that subscribe is just instead of find for example so I don't think include should be a problem and it is.
The text was updated successfully, but these errors were encountered: