GraphQL: le,lt,ge, gt on datetime work opposite way (ie. le as ge)

[picbeats]

Describe the bug
In GraphQL queries
le,lt,ge, gt on datetime work opposite way (ie. le as ge)

To Reproduce
Schema

[
  {
    "@type": "@context",
    "@documentation": {
      "@title": "",
      "@description": ""
    },
    "@schema": "terminusdb:///schema#",
    "@base": "terminusdb:///data/"
  },
  {
    "@type": "Class",
    "@id": "A",
    "@key": {
      "@type": "Lexical",
      "@fields": [
        "name"
      ]
    },
    "name": "xsd:string",
    "timestamp": {
      "@type": "Optional",
      "@class": "xsd:dateTime"
    }
  }
]

Data:

[
  {
    "@id": "A/a1",
    "@type": "A",
    "name": "a1",
    "timestamp": "2023-12-12T15:41:33.870064Z"
  },
  {
    "@id": "A/a2",
    "@type": "A",
    "name": "a2",
    "timestamp": "2023-12-12T16:41:33.870064Z"
  }
]

GraphQL query

query{
  A(filter:{timestamp:{ge:"2023-12-12T16:11:33.870064Z"}}) {
    timestamp
    name
  }
}

Result

{
  "data": {
    "A": [
      {
        "timestamp": "2023-12-12T15:41:33.870064Z",
        "name": "a1"
      }
    ]
  }
}

Expected behavior

Query should return record with name "a2" since it timestamp "2023-12-12T16:41:33.870064Z" is bigger that specified "2023-12-12T16:11:33.870064Z"

Similar issues with other comparison operators, looks like le, lt are swapped with ge,gt

Info (please complete the following information):

• Docker image TerminusDB v11.1.9 on WSL/Ubuntu22.04

Additional context
Add any other context about the problem here.

[GavinMendelGleason]

Fixed in #2058

[picbeats]

It's not the same bug. I checked #2058 changes, and while it does fix le vs lt it does not seems to me that it fixes opposite ordering of datetime. I'd expect lt with gt swap in the code. There is also apparently no test checking correct ordering for dateTime.

[GavinMendelGleason]

Aha!