-
-
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
PFQuery's whereKey:equalTo: function seems not working on Parse Server like before #175
Comments
The solution that I found is to use: |
But it should not. Array of objects can't be equal to object. |
See the answer of Héctor Ramos from Parse at this link: |
Ok, I was wrong, got it. But I can not call it good practice. |
I agree with you. An array of objects can't be equal to object. |
Hey @leobortolotti , this was reported as a bug as I noticed the same strange behaviour. #74 |
@edvincandon Got it. As I said, I found this solution too: |
This has been fixed in #284 |
…elation Added param to getRelation for Issue 126
hey, i have 2.0.8 installed but it seems still not fixed. this is my query:
this is how data stored in db:
but it works with:
did i miss something? |
Hi, @drew-gross Recently, I tried to migrate my app to parse-server and met this issue. My parse-server version is I have a class called I tried
returned nothing, but with
it worked. I checked my Is there any idea why this issue still exist? |
I'm seeing the same as @alioguzhan and @kenkuan. Am using a hosted Parse server of version 2.2.19, calling from iOS SDK v.1.14.2 (from cocoapods) and a query that worked against the original Parse service no longer works. Key 'userAck' has a value of and before a query of: Now it gets 0 matches and I have to change it to And while the revised syntax does make more sense it means I've got an unknown about of broken queries throughout my code base, and previously documented behaviour has changed. The above reported fix #284 does not seem to have worked for several of us. |
Has this been resolved? I'm just now running into this issue via JS query.equalTo() |
Updated mongodb-core to 2.1.10 NODE-981 delegate auth to replset/mongos if inTopology is set. NODE-978 Wrap connection.end in try/catch for node 0.10.x issue causing exceptions to be thrown, Also surfaced getConnection for mongos and replset. Remove dynamic require (Issue parse-community#175, https://github.com/tellnes). NODE-696 Handle interrupted error for createIndexes. Fixed isse when user is executing find command using Server.command and it get interpreted as a wire protcol message, parse-community#172. NODE-966 promoteValues not being promoted correctly to getMore. Merged in fix for flushing out monitoring operations. NODE-983 Add cursorId to aggregate and listCollections commands (Issue, parse-community#1510). Mark group and profilingInfo as deprecated methods NODE-956 DOCS Examples. Update readable-stream to version 2.2.7. NODE-978 Added test case to uncover connection.end issue for node 0.10.x. NODE-972 Fix(db): don't remove database name if collectionName == dbName (Issue, parse-community#1502) Fixed merging of writeConcerns on db.collection method. NODE-970 mix in readPreference for strict mode listCollections callback. NODE-966 added testcase for promoteValues being applied to getMore commands. NODE-962 Merge in ignoreUndefined from collection level for find/findOne. Remove multi option from updateMany tests/docs (Issue parse-community#1499, https://github.com/spratt). NODE-963 Correctly handle cursor.count when using APM.
Updated mongodb-core to 2.1.10 NODE-981 delegate auth to replset/mongos if inTopology is set. NODE-978 Wrap connection.end in try/catch for node 0.10.x issue causing exceptions to be thrown, Also surfaced getConnection for mongos and replset. Remove dynamic require (Issue #175, https://github.com/tellnes). NODE-696 Handle interrupted error for createIndexes. Fixed isse when user is executing find command using Server.command and it get interpreted as a wire protcol message, #172. NODE-966 promoteValues not being promoted correctly to getMore. Merged in fix for flushing out monitoring operations. NODE-983 Add cursorId to aggregate and listCollections commands (Issue, #1510). Mark group and profilingInfo as deprecated methods NODE-956 DOCS Examples. Update readable-stream to version 2.2.7. NODE-978 Added test case to uncover connection.end issue for node 0.10.x. NODE-972 Fix(db): don't remove database name if collectionName == dbName (Issue, #1502) Fixed merging of writeConcerns on db.collection method. NODE-970 mix in readPreference for strict mode listCollections callback. NODE-966 added testcase for promoteValues being applied to getMore commands. NODE-962 Merge in ignoreUndefined from collection level for find/findOne. Remove multi option from updateMany tests/docs (Issue #1499, https://github.com/spratt). NODE-963 Correctly handle cursor.count when using APM.
Hi,
Inside Parse I have a key where I store an array of Pointers. Then I use the PFQuery's function whereKey:equalTo: like this:
[query whereKey:@"members" equalTo:[PFUser currentUser]];
The problem is that when it was Parse hosted, it was working well. But now with Parse Server it isn't working. It isn't retrieving the objects from Class that have [PFUser currentUser] inside the key's array.
Is it a bug in Parse Server?
The text was updated successfully, but these errors were encountered: