You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,31 @@
3
3
## Next release
4
4
(Add entries here in the order of: server, console, cli, docs, others)
5
5
6
+
### Transactions for Postgres mutations
7
+
8
+
With v2 came the introduction of heterogeneous execution: in one query or mutation, you can target different sources: it is possible, for instance, in one mutation, to both insert a row in a table in a table on Postgres and another row in another table on MSSQL:
insert_publication_one(object: {name: "Template meta-programming for Haskell"}) {
19
+
name
20
+
}
21
+
}
22
+
```
23
+
24
+
However, heterogeneous execution has a cost: we can no longer run mutations as a transaction, given that each part may target a different database. This is a regression compared to v1.
25
+
26
+
While we want to fix this by offering, in the future, an explicit API that allows our users to *choose* when a series of mutations are executed as a transaction, for now we are introducing the following optimisation: when all the fields in a mutation target the same Postgres source, we will run them as a transaction like we would have in v1.
27
+
28
+
29
+
### Bug fixes and improvements
30
+
6
31
- server: add `--async-actions-fetch-interval` command-line flag and `HASURA_GRAPHQL_ASYNC_ACTIONS_FETCH_INTERVAL` environment variable for configuring
7
32
async actions re-fetch interval from metadata storage (fix #6460)
8
33
- server: add 'replace_configuration' option (default: false) in the add source API payload
0 commit comments