mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix typo

Browse Source
This commit is contained in:
Andrew Dunstan 2006-05-28 03:12:00 +00:00
parent 3a9ae3d206
commit 7a6676d9df
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/test/regress/expected/triggers.out
View File

@ -403,7 +403,7 @@ begin
relid := TG_relid::regclass; 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, -- can, or by a sort of reflection like tcl can,
-- so we have to hard code the names. -- so we have to hard code the names.
raise NOTICE 'TG_NAME: %', TG_name; raise NOTICE 'TG_NAME: %', TG_name;
@ -433,6 +433,7 @@ begin
if TG_OP != 'DELETE' then if TG_OP != 'DELETE' then
raise NOTICE 'NEW: %', NEW; raise NOTICE 'NEW: %', NEW;
end if; end if;
if TG_OP = 'DELETE' then if TG_OP = 'DELETE' then
return OLD; return OLD;
else else

3
src/test/regress/sql/triggers.sql
View File

@ -314,7 +314,7 @@ begin
relid := TG_relid::regclass; 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, -- can, or by a sort of reflection like tcl can,
-- so we have to hard code the names. -- so we have to hard code the names.
raise NOTICE 'TG_NAME: %', TG_name; raise NOTICE 'TG_NAME: %', TG_name;
@ -344,6 +344,7 @@ begin
if TG_OP != 'DELETE' then if TG_OP != 'DELETE' then
raise NOTICE 'NEW: %', NEW; raise NOTICE 'NEW: %', NEW;
end if; end if;
if TG_OP = 'DELETE' then if TG_OP = 'DELETE' then
return OLD; return OLD;
else else