Changelog
Heroku Postgres compatibility
Heroku recently changed their Postgres extension schema management: https://devcenter.heroku.com/changelog-items/2446
In this release, we have added functionality to customize where pgcrypto
is installed namely via HASURA_GRAPHQL_METADATA_DATABASE_EXTENSIONS_SCHEMA
(for metadata db) and extensions_schema
source db metadata (if using event triggers).
See more in the following section.
Bug fixes and improvements
- server: accept
extensions_schema
while adding a PostgreSQL source for the graphql-engine to install database extensions in the specified schema (fixes #8734) - server: accept a default extensions schema (
HASURA_GRAPHQL_METADATA_DATABASE_EXTENSIONS_SCHEMA
) for the metadata database where graphql-engine will install database extensions (#3657) - server: add warning log for missing admin secret
- server: fix querying relationships defined using multiple columns on BigQuery
- console: add custom names for streaming subscriptions
- console: add support for table query and subscription root fields visibility permissions
- console: fix the BigQuery row-level restrictions on boolean columns
- console: add support extensions_schema on postgres connect/edit DB form
- console: add support for new database-to-remote schema metadata format in old table relationships UI