Ashok Das

@carlosbaraza Looks like the sort operation in your query (name DESC) is the most expensive, please see if it can be optimized by creating an index on that field that...

The issue seems related to [8961](https://github.com/hasura/graphql-engine/issues/8961), which has been fixed recently and will be part of "v2.13.0-beta.1 " due to be released today/tomorrow.

@Aiden0 Can you retry the same from a newer version of graphql-engine (e.g. v2.11.0) ? The reason is, I did a quick test with a Hasura Cloud and got a...

@Aiden0 Thanks for trying out all the scenarios. Looks like we have a viable workaround to use "[{}]" for an empty array. Please close the ticket if you are ok...

@DomVinyard Actually, what you are seeing are two different database schemas: **metadata** and **main database**. You should see distinct values in "table_catalog" column in the above sql query. Hasura Metadata...

@DomVinyard Thank you for your prompt update. We have created a separate [feature request](https://github.com/hasura/graphql-engine/issues/9135) for an API and intimated the engineering team. You should be able to track its progress.

@DomVinyard We would like to share with you an internal API to get count of scheduled events. This one is not documented yet, so here is its usage example (as...

Do you have column-level permissions set for the mentioned computed field(s) ? Here is the link to the doc for your reference: https://hasura.io/docs/latest/schema/postgres/computed-fields/#computed-fields-permissions

Unfortunately, ordering results by computed fields is not currently supported. There is an open Github [issue](https://github.com/hasura/graphql-engine/issues/4356) on this. You may be interested in the suggested workaround in the issue as...

@MorningK Glad you were able to find the cause of your issue. Please close the issue if it is no longer persistent.