Changelog

Breaking Fixes

• This fix changes the behavior of aggregate queries when used in conjunction with the limit configuration in select permissions. In versions prior to this, aggregate functions account for the value of the limit setting when calculating the aggregate value. This will not be the case going forward and aggregate values will calculated over all the rows that the role has permissions for. (fix #1837) (#2027)

  E.g.: Assuming a role has permissions to access all the rows in the authors table and the limit configuration is set to 2. Query:

  {
    authors {
      id
      num_articles
    }
    authors_aggregate {
      aggregate {
        max {
          num_articles
        }
      }
    }
  }

  Before the fix:

  {
    "data": {
      "authors": [
        {
          "id": 1,
          "num_articles": 1
        },
        {
          "id": 2,
          "num_articles": 2
        }
      ],
      "authors_aggregate": {
        "aggregate": {
          "max": {
            "num_articles": 2
          }
        }
      }
    }
  }

  After the fix:

  {
    "data": {
      "authors": [
        {
          "id": 1,
          "num_articles": 1
        },
        {
          "id": 2,
          "num_articles": 2
        }
      ],
      "authors_aggregate": {
        "aggregate": {
          "max": {
            "num_articles": 5
          }
        }
      }
    }
  }

Bug Fixes

• Server now adds variable name to the path when there is an error. Earlier, the path key in the error response when there is an issue with variables was just $.variableValues. Now, it includes the variable name as well, like $.variableValues.<var_name>. (close #2050) (#2051)
• Fixes a bug that allowed null values for non-nullable fields. (close #1981) (#2057)
• Fixes a bug on server that allowed dropping of columns that were used in the permissions rules with column operators. (close #2054) (#2055)
• Fixes a bug that caused server to send duplicate headers to remote schema server. (#2118)
• Fixes a bug that caused server not to update the GraphQL Schema when a column's nullability or type is changed. (fix #2101) (#2106)

New Features

• Server adds a new API to execute pg_dump on the connected Postgres server. The migrations workflow has improved a lot because of this. To get the schema and metadata from a server, only one CLI command is enough. See docs for more details. (close #1939) (#1967)

  hasura migrate create "init" --from-server

Other changes

• server: multiplexed subscription improvements (#2081)
• server: log inconsistent metadata objects only when there are any (close #2053) (#2058)
• server: schema cache sync improvements (#2098)
• console: change Github to GitHub at multiple places (#2046)
• console: fix console bugs (close #2030, #2032, #226) (#2044)
• console: change position of constraint names in table modify (#2070)
• console: restructure console files (#2078)
• console: fix console expandable editor styles (#2111)
• console: fix set column as unique bug (close #2096) (#2108)