hasura / hasura/graphql-engine

Wrong order in action result with nested object relation

Open
#7,701 1 comment 2 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version:
CLI Version (for CLI related issue): hasura/graphql-engine:v2.0.9.cli-migrations-v2

### Environment

Self-hosted on AWS ECS

### What is the expected behaviour?

Action result order is preserved upon including nested objects:
![image](https://user-images.githubusercontent.com/2305853/137887327-d7694ba3-b311-4b37-8584-1d397ca5e522.png)
![image](https://user-images.githubusercontent.com/2305853/137887493-6f4cb5be-8e04-4424-802e-597b2f09d791.png)

### Keywords

order

### What is the current behaviour?

In some cases the order is messed up:
![image](https://user-images.githubusercontent.com/2305853/137887570-5afb0b1a-b858-4e4c-94e5-e731d7c6dd78.png)

### How to reproduce the issue?

1. Create an Action which returns array of object ids and set up an appropriate object relation;
2. Run queries from above
3. Sometimes (_when including only the nested object_ in my case) the order is messed up

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.