Description

The issue came from the recent refactor of internal types of Select modules. Any of existing test cases didn't catch it because

1. The query need to be requested as non-admin role
2. The object relationship whose permission limit defined should be queried in table selection set and be present in order by clause

query topic {
  topic (order_by: { category: {importance: desc}}) {
      {
       id
       category {
           id
      }
  }
}

Cause: In generated SQL, sub queries for object relationships from same table are grouped together. Unfortunately, this was not happening for object relationships present in order by clause and selection set if any permission limit set. The permission limit was considered into the identifier and hence both order by and selection set object relationship fields are treated different.

Changelog

• CHANGELOG.md is updated with user-facing content relevant to this PR. If no changelog is required, then add the no-changelog-required label.

No changelog required since the bug doesn't exist in previous stable releases.

Affected components

• Server
• Tests

Related Issues

Solution and Design

Refactor object relationship types without considering the permission limits.

Steps to test and verify

Limitations, known bugs & workarounds

Server checklist

Catalog upgrade

Does this PR change Hasura Catalog version?

• No
• Yes

Metadata

Does this PR add a new Metadata feature?

• No
• Yes

GraphQL

• No new GraphQL schema is generated
• New GraphQL schema is being generated

Breaking changes

• No Breaking changes
• There are breaking changes