docs: add note on computed fields not being part of event trigger payload

GITHUB_PR_NUMBER: 7816
GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/7816

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2888
Co-authored-by: Vildan Softic <2861414+zewa666@users.noreply.github.com>
Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com>
GitOrigin-RevId: 816574a4228a396ebc8bcdfe1a6acd9d7be87bba
This commit is contained in:
hasura-bot 2021-11-25 18:08:27 +05:30
parent a3076a3f64
commit 1519b66c4c

View File

@ -108,10 +108,12 @@ JSON payload
.. note::
In case of ``UPDATE``, the events are delivered only if new data is distinct from
old data. The `composite type comparison <https://www.postgresql.org/docs/current/functions-comparisons.html#COMPOSITE-TYPE-COMPARISON>`__
is used to compare the old and new rows. If rows contain columns, which cannot be
compared using ``<>`` operator, then internal binary representation of rows by Postgres is compared.
- In case of ``UPDATE``, the events are delivered only if new data is distinct from
old data. The `composite type comparison <https://www.postgresql.org/docs/current/functions-comparisons.html#COMPOSITE-TYPE-COMPARISON>`__
is used to compare the old and new rows. If rows contain columns, which cannot be
compared using ``<>`` operator, then internal binary representation of rows by Postgres is compared.
- :ref:`Table computed fields <computed_fields>` are not included in the event trigger payload data
**For example**:
@ -121,7 +123,7 @@ JSON payload
"id": "85558393-c75d-4d2f-9c15-e80591b83894",
"created_at": "2018-09-05T07:14:21.601701Z",
"trigger": {
"name": "test_trigger"
"name": "insert_user_trigger"
},
"table": {
"schema": "public",
@ -144,8 +146,6 @@ JSON payload
}
}
Syntax definitions
------------------