Changelog

Streaming subscriptions

Streaming subscriptions can be used to subscribe only to the data which has been changed in the query. The streaming is done on the basis of a cursor, which is chosen by the user.

Request payload:

subscription GetUserLatestMessages ($user_id: uuid!) {
  messages_stream (cursor: {initial_value: {id: 0}, ordering: ASC}, batch_size: 1, where: {user_id: {_eq: $user_id}} ) {
    id
    from
    to
  }
}

The above subscription streams the messages of the user corresponding to the user_id in batches of 1 message per batch.

Suppose there are two messages to be streamed, then the server will send two responses as following:

Response 1:

{
  "data": [
    {
      "id": 1,
      "from": 155234,
      "to": 155523
    }
  ]
}

Response 2:

{
  "data": [
    {
      "id": 5,
      "from": 178234,
      "to": 187523
    }
  ]
}

Bug fixes and improvements

• server: don't drop the SQL triggers defined by the graphql-engine when DDL changes are made using the run_sql API
• server: fixed a bug where timestamp values sent to postgres would erroneously trim leading zeroes (#8096)
• server: fix bug when event triggers where defined on tables that contained non lower-case alphabet characters
• server: avoid encoding 'varchar' values to UTF8 in MSSQL backends
• server: add support for MSSQL event triggers (#7228)
• server: update pg_dump to be compatible with postgres 14 (#7676)
• server: Don't drop nested typed null fields in actions (fix #8237)
• server: fixes url/query date variable bug in REST endpoints
• server: makes url/query variables in REST endpoints assume string if other types not applicable
• server: fix inserting empty objects with default values to postgres, citus, and sql server (fix #8475)
• console: bug fixes for RS-to-RS relationships
• console: allow users to remove prefix / suffix / root field namespace from a remote schema
• console: new "add remote schema" page (with GQL customization)
• console: fix console crash on adding pg sources with connection params through api
• cli: avoid exporting hasura-specific schemas during hasura init (#8352)
• cli: fix performance regression in migrate status command (fix #8398)