Description

The re-modeled check permissions for insert and update (see #3804, #3598) generates the INSERT and UPDATE SQL CTE statement by RETURNING * and an extra column which invokes the check permission exception on invalidation (see note [Mutation output expression] in the diff) . This causes the output rows from the mutation CTE to contain an extra column and cannot typecast to table row type for the computed field function's input. Hence the Postgres query is failing. This PR fixes the same.

Changelog

• CHANGELOG.md is updated with user-facing content relevant to this PR.

Affected components

• Server
• Console
• CLI
• Docs
• Community Content
• Build System
• Tests
• Other (list it)

Related Issues

Fix #4035

Solution and Design

In the SQL statement which generates the mutation output, add a CTE which extracts only table columns in the order of their ordinal positions. This will ensure the input for computed field will be cast-able to table rowtype. See note [Mutation output expression] in Hasura.RQL.DML.Returning module.

Steps to test and verify

Reproduce the issue #4035, 'postgres query error' shouldn't happen.

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