Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit5a67d76

Browse files
committed
Clarify trigger function return convention, per Thomas Hallgren.
1 parent79f9ee9 commit5a67d76

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

‎doc/src/sgml/trigger.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.35 2004/03/03 22:22:24 neilc Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.36 2004/08/13 16:17:19 tgl Exp $
33
-->
44

55
<chapter id="triggers">
@@ -431,8 +431,10 @@ typedef struct Trigger
431431
</para>
432432

433433
<para>
434-
A trigger function must return either <symbol>NULL</> or a
435-
<structname>HeapTuple</> pointer. Be careful to return either
434+
A trigger function must return either a
435+
<structname>HeapTuple</> pointer or a <symbol>NULL</> pointer
436+
(<emphasis>not</> a SQL NULL, that is, do not set isNull true).
437+
Be careful to return either
436438
<structfield>tg_trigtuple</> or <structfield>tg_newtuple</>,
437439
as appropriate, if you don't want to modify the row being operated on.
438440
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp