Commit469150a

committed

Doc: clarify how triggers relate to transactions.

1 parent2dc53fe commit469150aCopy full SHA for 469150a

File tree

+13

-0

lines changed

+13

-0

lines changed

Lines changed: 4 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -175,6 +175,10 @@ CREATE [ OR REPLACE ] [ CONSTRAINT ] TRIGGER <replaceable class="parameter">name`
`175`	`175`	`</para>`
`176`	`176`
`177`	`177`	`<para>`
	`178`	`+ <indexterm>`
	`179`	`+ <primary>trigger</primary>`
	`180`	`+ <secondary>constraint trigger</secondary>`
	`181`	`+ </indexterm>`
`178`	`182`	`When the <literal>CONSTRAINT</literal> option is specified, this command creates a`
`179`	`183`	`<firstterm>constraint trigger</firstterm>. This is the same as a regular trigger`
`180`	`184`	`except that the timing of the trigger firing can be adjusted using`

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -122,6 +122,15 @@`
`122`	`122`	`row in the view is identified as needing to be operated on.`
`123`	`123`	`</para>`
`124`	`124`
	`125`	`+ <para>`
	`126`	`+ The execution of an <literal>AFTER</literal> trigger can be deferred`
	`127`	`+ to the end of the transaction, rather than the end of the statement,`
	`128`	`+ if it was defined as a <firstterm>constraint trigger</firstterm>.`
	`129`	`+ In all cases, a trigger is executed as part of the same transaction as`
	`130`	`+ the statement that triggered it, so if either the statement or the`
	`131`	`+ trigger causes an error, the effects of both will be rolled back.`
	`132`	`+ </para>`
	`133`	`+`
`125`	`134`	`<para>`
`126`	`135`	`A statement that targets a parent table in an inheritance or partitioning`
`127`	`136`	`hierarchy does not cause the statement-level triggers of affected child`

Comments

(0)