Benoit Ranque

Bumping this, @kitten would you like me to go ahead and PR this change?

Most likely the issue is providing both the `--database-url` and the `--metadata-database-url` flags. Try this command instead: ```bash CMD HASURA_GRAPHQL_METADATA_DATABASE_URL=$DATABASE_URL graphql-engine \ --metadata-database-url $DATABASE_URL \ serve \ --server-port $PORT ```

Am able to confirm this issue persists as of hasura 2.12.0

@sassela Apologies, only seeing this now. You should be able to repro this issue with any query of the form ```gql query { table1 { computed_table_field { table2 { scalar_field...

I've reproduced this in cases where some rows have special characters that seem to confuse the serializer. To workaround this, you can download the JSON file instead, and then convert...

The issue has been identified and a fix has been developed. We expect this fix to be available in release 2.14

@dannick-hasura an important note: renaming the `update_many` mutation does not solve this problem, as the issue is not with the mutation root field per-se, rather it is with the associated...

@sassela because the conflicts is with the generated types, renaming root fields is not a sufficient workaround. However, it is possible to rename the conflicting table, then rename root fields...

Tested this, able to reproduce. It looks like the roles' row limit is being treated as the total number of rows, which is incorrect. To reproduce this: - set a...

Hi @DomVinyard ### How to get count of events The short answer to your question: > is it undocumented for a reason, aka should I not be interfacing with it...