40th alpha release for v1.0.0
Pre-release
Pre-release
·
9080 commits
to master
since this release
Changelog
Update on 14 March 2019:
🚨 🚨 Breaking change 🚨 🚨
From alpha40, relationships/nested objects can be retrieved in mutations ONLY if the table has a primary key or a unique constraint. The approach taken prior to alpha40 would only work in some cases and could trigger inconsistent results such as those documented in #1576.
- Please add either a primary key or a unique constraint to tables with such mutations.
- If you are using updatable views, you can either have mutations on the underlying tables directly or you can downgrade to
alpha39by following these instructions:- Stop graphql-engine alpha40
- Run this SQL on your database:
DROP TABLE hdb_catalog.hdb_schema_update_event; DROP FUNCTION hdb_catalog.hdb_schema_update_event_notifier(); UPDATE hdb_catalog.hdb_version SET version = '10';
- Start graphql-engine alpha39
We are looking into inferring the constraints on an updatable view from the underlying base table asap.
Sorry about missing this in the previous announcement! If you need any help with this, please reach out to @team hasura on the #general channel on Discord.
🎁 🎁 New features 🎁 🎁
- The server can now sync metadata changes across multiple instances. Previously, if there were more than one Hasura instances connected to a database, metadata had to be reloaded on all instances of Hasura when migrations were applied or if the schema was changed via one of the Hasura instances. With this release, updating schema on one instance emits an event that other instances will listen to and reload the metadata automatically. (closes #1182) (#1574)
- Server now respects
x-hasura-headers for unauthorized role permissions (close #1686) (#1689)
🐛 🐛 Bug fixes 🐛 🐛
- Queries/Mutations on remote schema now works over websocket. (fix #1619) (#1621)
- Mutation now returns the updated data over relationships (fix #1576) (#1703)