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

Commit7ac5727

Browse files
committed
Fix wording of section comparing triggers and rules; old wording as
confusing.
1 parent794ec7b commit7ac5727

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

‎doc/src/sgml/rules.sgml

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.51 2007/02/01 19:10:24 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.52 2008/12/16 03:12:08 momjian Exp $ -->
22

33
<chapter id="rules">
44
<title>The Rule System</title>
@@ -1869,13 +1869,9 @@ GRANT SELECT ON phone_number TO secretary;
18691869
</para>
18701870

18711871
<para>
1872-
On the other hand, a trigger that is fired on
1873-
<command>INSERT</command> on a view can do the same as a rule: put
1874-
the data somewhere else and suppress the insert in the view. But
1875-
it cannot do the same thing on <command>UPDATE</command> or
1876-
<command>DELETE</command>, because there is no real data in the
1877-
view relation that could be scanned, and thus the trigger would
1878-
never get called. Only a rule will help.
1872+
On the other hand, a trigger cannot be created on views because
1873+
there is no real data in a view relation; however INSERT, UPDATE,
1874+
and DELETE rules can be created on views.
18791875
</para>
18801876

18811877
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp