From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/trigger-definition.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/trigger-definition.html') diff --git a/doc/src/sgml/html/trigger-definition.html b/doc/src/sgml/html/trigger-definition.html index f0eae81..5e4f613 100644 --- a/doc/src/sgml/html/trigger-definition.html +++ b/doc/src/sgml/html/trigger-definition.html @@ -1,5 +1,5 @@ -39.1. Overview of Trigger Behavior
39.1. Overview of Trigger Behavior
Prev UpChapter 39. TriggersHome Next

39.1. Overview of Trigger Behavior

+39.1. Overview of Trigger Behavior

39.1. Overview of Trigger Behavior
Prev UpChapter 39. TriggersHome Next

39.1. Overview of Trigger Behavior

A trigger is a specification that the database should automatically execute a particular function whenever a certain type of operation is performed. Triggers can be attached to tables (partitioned or not), @@ -312,4 +312,4 @@ that is being used, but the typical approach is to make the transition tables act like read-only temporary tables that can be accessed by SQL commands issued within the trigger function. -

Prev Up Next
Chapter 39. Triggers Home 39.2. Visibility of Data Changes
\ No newline at end of file +

Prev Up Next
Chapter 39. Triggers Home 39.2. Visibility of Data Changes
\ No newline at end of file -- cgit v1.2.3