-
Notifications
You must be signed in to change notification settings - Fork 146
[BUG] Nested ordering errors #272
Comments
Could you share your GraphQL type definitions so I can try to reproduce? (or at least the Chat and message types). I'm assuming |
|
I'm facing the same problem with a DateTime field. Any news on this? |
Hey, we are also dealing with this issue. We would like to refactor our code base to use Temporal values like
In our case, the
and the error thrown in the console is
Here is our
Wanna say a big thank you to @johnymontana and the other contributors to this library. |
Has anyone found a workaround or fix for this issue? |
Thanks for pinging this @g3rd - will try to address it this week. I suppose a temporary workaround might be to store an additional property that is the epoch milliseconds version of the timestamp as a Long and use that for ordering instead of the DateTime field? |
I am facing the same problem on spatial |
The proposed workaround works! Thanks! |
This issue still occurs in 2.16.3 with nested requests such as: query ($id: ID!, $first: Int!, $offset: Int!) {
User(id: $id) {
posts(first: $first, offset: $offset, orderBy: createdAt_desc) {
id
}
}
} |
Hi You can follow the instructions here : https://neo4j.com/labs/apoc/4.1/installation/ |
I installed https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/tag/4.1.0.2 the issue persists |
Sorting by date works when you requesting it only from one entity:
But if you requesting it on more entities, than it fails:
and gives following error: |
When i try to order the values of a related entity it throws an error:
Get this error:
We are using:
The text was updated successfully, but these errors were encountered: