Skip to content

.notEqualsTo Parse.Query-function weirdness on postgres (for nested objects) #6403

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

Open
coderofsalvation opened this issue Feb 12, 2020 · 1 comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@coderofsalvation
Copy link

coderofsalvation commented Feb 12, 2020

#6177 # Issue Description

.notEqualsTo Parse.Query-function not behaving correctly on postgres (for nested objects)

Steps to reproduce

        var q1 = new Parse.Query("MyClass").equalTo("state.status","open")
        var q2 = new Parse.Query("MyClass").equalTo("state.foo",6)
        await Parse.Query.and(q1,q2).find()

        => [s] // correct

just changing .equalTo to .notEqualTo does not seem to differ at all.

        var q1 = new Parse.Query("MyClass").equalTo("state.status","open")
+++     var q2 = new Parse.Query("MyClass").notEqualTo("state.foo",6)
        await Parse.Query.and(q1,q2).find()

?       => [s]       // should be []

another simplified version:

        await new Parse.Query("MyClass")
        .equalTo("state.status","open")
        .equalTo("state.foo",6).find()

        => [s]      

        await new Parse.Query("MyClass")
        .equalTo("state.status","open")
+++     .notEqualTo("state.foo",6).find()

?       => [s]       // should be []

Environment Setup

  • parse-server version: 3.9.0
  • Operating System: alpine linux 3
  • Localhost or remote server? localhost
  • Postgres version: 11.5
  • Storage engine: Postgres
@davimacedo davimacedo added the type:bug Impaired feature or lacking behavior that is likely assumed label Feb 12, 2020
@stale
Copy link

stale bot commented Nov 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

3 participants