-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
PFQuery orQueryWithSubqueries not working #550
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
Comments
Are any of those queries involving a relation field? It could be the same issue I'm facing. #432 |
Hey, I'm facing the same issue with iOS, while my console prints: Looks like an issue with the ParseServer. |
I'm having a related issue and I think it's because the relation doesn't exist in my case. Does the relation field exist in your parse server database? For example if the relation field that you're querying on is "likes" for the user likes, that relation must be created first. I'm not sure how that's created though. |
Yeah that is exactly what happens to me.
|
Its a migrated app, so it shouldn't happen, Any news with it? |
@gfosco any insight into the functionality of |
|
$relatedTo is supported, at least partially (see ExportAdapter L455)... can you provide the rest formatted query you're submitting? |
|
Hi all. |
@nathan-savvy can you try with that commit. Your query seems to be very complex, and building a test just for it seems overkill but I'll try |
@flovilmart Thank you, I will try it on Friday and let you know how it goes! |
@flovilmart I am still receiving an error when trying to run an or query, after updating to the latest verion of Parse Server: |
@dcdspace I'm onto it, can you give me the js/swift/objc-c code for your query? It seems to be occurring on very complex queries |
@nathan-savvy I've reproduced the query you're running with the master branch:
And it seems to run properly, not throwing error anymore. |
@flovilmart You're the man. Much appreciated. |
I take that as it's working now? |
Sorry, I mean thank you for testing the query. I won't be able to give it an official test until tomorrow (busy week). |
no problemo |
@flovilmart - thanks again `
|
Is that resolved for everyone running on master? |
@flovilmart This resolved our issue. Thanks again. |
@flovilmart This solved ours also! THANKS A LOT!!!!!! |
Hi guys, on parse-server 2.4.2 I am experiencing a very similar issue, you might reproduce it with the following snippet
I got exactly the same error
the original intention was to use the
but I realised that when one of the relations is I think an empty relation (and therefore an empty result set) is a feasible use case that should be supported. Am I missing something guys? Many thanks for reading |
Anything wrong with my attempt @flovilmart? If I am right about my assumptions I am happy to submit a PR to fix it |
@jaimeagudo you're more than encouraged to submit a PR! |
In my iOS app, I have this line of code
PFQuery *totalQuery = [PFQuery orQueryWithSubqueries:@[queryClosed, query, pendingQuery, openQuery]];
that used to work, but after adding the new client configuration to my own parse server, it doesn't execute. Is this a bug with parse server?The text was updated successfully, but these errors were encountered: