Postgres: GraphQL Mutations

Introduction

GraphQL mutations are used to modify data on the server (i.e. write, update or delete data).

Hasura GraphQL Engine auto-generates mutations as part of the GraphQL schema from your Postgres schema model.

Data of all tables in the database tracked by the GraphQL Engine can be modified over the GraphQL endpoint. If you have a tracked table in your database, its insert/update/delete mutation fields are added as nested fields under the mutation_root root level type.

Postgres Compatibility

Hasura works with most Postgres compatible flavours.

Types of mutation requests

The following types of mutation requests are possible:

• Insert
• Upsert
• Update
• Delete
• Multiple mutations in a request

Other configuration

By default, Hasura treats unset nullable variables with no default as being nulls. However, according to the GraphQL specification, these values should be removed from the query. Thus, with the experimental feature flag no_null_unbound_variable_default, users can opt into this behavior.