From 7a6676d9df6e89d6ecdfacd8b377a881dc0e237d Mon Sep 17 00:00:00 2001 From: Andrew Dunstan Date: Sun, 28 May 2006 03:12:00 +0000 Subject: [PATCH] fix typo --- src/test/regress/expected/triggers.out | 3 ++- src/test/regress/sql/triggers.sql | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/src/test/regress/expected/triggers.out b/src/test/regress/expected/triggers.out index 6d8a436f50..d8b0594c2b 100644 --- a/src/test/regress/expected/triggers.out +++ b/src/test/regress/expected/triggers.out @@ -403,7 +403,7 @@ begin relid := TG_relid::regclass; - -- plpgsql can't discover it's trigger data in a hash like perl and python + -- plpgsql can't discover its trigger data in a hash like perl and python -- can, or by a sort of reflection like tcl can, -- so we have to hard code the names. raise NOTICE 'TG_NAME: %', TG_name; @@ -433,6 +433,7 @@ begin if TG_OP != 'DELETE' then raise NOTICE 'NEW: %', NEW; end if; + if TG_OP = 'DELETE' then return OLD; else diff --git a/src/test/regress/sql/triggers.sql b/src/test/regress/sql/triggers.sql index fc688a08f9..909a7d68d9 100644 --- a/src/test/regress/sql/triggers.sql +++ b/src/test/regress/sql/triggers.sql @@ -314,7 +314,7 @@ begin relid := TG_relid::regclass; - -- plpgsql can't discover it's trigger data in a hash like perl and python + -- plpgsql can't discover its trigger data in a hash like perl and python -- can, or by a sort of reflection like tcl can, -- so we have to hard code the names. raise NOTICE 'TG_NAME: %', TG_name; @@ -344,6 +344,7 @@ begin if TG_OP != 'DELETE' then raise NOTICE 'NEW: %', NEW; end if; + if TG_OP = 'DELETE' then return OLD; else -- 2.11.0