Skip to content

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

Open
@coderofsalvation

Description

@coderofsalvation

#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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions