From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/trigger-datachanges.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/trigger-datachanges.html') diff --git a/doc/src/sgml/html/trigger-datachanges.html b/doc/src/sgml/html/trigger-datachanges.html index 68614aa..9379840 100644 --- a/doc/src/sgml/html/trigger-datachanges.html +++ b/doc/src/sgml/html/trigger-datachanges.html @@ -1,5 +1,5 @@ -39.2. Visibility of Data Changes
39.2. Visibility of Data Changes
Prev UpChapter 39. TriggersHome Next

39.2. Visibility of Data Changes

+39.2. Visibility of Data Changes

39.2. Visibility of Data Changes
Prev UpChapter 39. TriggersHome Next

39.2. Visibility of Data Changes

If you execute SQL commands in your trigger function, and these commands access the table that the trigger is for, then you need to be aware of the data visibility rules, because they determine @@ -43,4 +43,4 @@

Further information about data visibility rules can be found in Section 47.5. The example in Section 39.4 contains a demonstration of these rules. -

Prev Up Next
39.1. Overview of Trigger Behavior Home 39.3. Writing Trigger Functions in C
\ No newline at end of file +

Prev Up Next
39.1. Overview of Trigger Behavior Home 39.3. Writing Trigger Functions in C
\ No newline at end of file -- cgit v1.2.3