You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
For information, the same bug is also affecting queries on Relations when trying to fetch records from the inversed side of the relationship with a recent version of the server.
// suppose we have a author object, for which we want to get all books$author = ...
// first we will create a query on the Book object
$query = newParseQuery("Book");
// now we will query the authors relation to see if the author object we have// is contained therein$query->equalTo("authors", $author);
The SDK is sending a "where authors $eq: {}" instead of "authors: {}"
Environment
Parse PHP SDK
SDK version: 2.3.2
PHP version: 8.1.18
Server
Parse Server version: 6.1.0
Operating system: Ubuntu
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local
Database
System (MongoDB or Postgres): MongoDB
Database version: 5.0.18
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local
zeliard91
added a commit
to zeliard91/DoctrineParseBundle
that referenced
this issue
May 30, 2023
New Issue Checklist
We're not running the latest Parse server version, hence I haven't checked the last item above.
Issue Description
The fix for
equalTo
in 2.3.1 broke queries on array values.Steps to reproduce
For example, to fetch all roles for a specific user:
Actual Outcome
In previous versions, the query sent to Parse would look like:
Which would give us the roles for that user back.
Expected Outcome
In 2.3.1 the query became:
Which does not give any roles back.
users
on_Role
is an array with a single user in our case.Environment
Parse PHP SDK
Server
Database
The text was updated successfully, but these errors were encountered: