diff options
| author | Bruce Momjian <bruce@momjian.us> | 2025-11-08 09:49:43 -0500 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2025-11-08 09:49:43 -0500 |
| commit | 980a855c5c2e21e964a739694e24004f72e03fdf (patch) | |
| tree | 6f431d946445c84073afff474c26dbf0e0ed28d3 /doc/src/sgml/ref/create_trigger.sgml | |
| parent | e8bfad4ca842733b957c01e732ec009778f952cd (diff) | |
doc: consistently use "structname" and "structfield" markup
Previously "literal" and "classname" were used, inconsistently, for
SQL table and column names.
Reported-by: Peter Smith
Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+Pvtf24r+bdPgBind84dBLPvgNL7aB+=HxAUupdPuo2gRg@mail.gmail.com
Backpatch-through: master
Diffstat (limited to 'doc/src/sgml/ref/create_trigger.sgml')
| -rw-r--r-- | doc/src/sgml/ref/create_trigger.sgml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index 0d8d463479b..bb1426f4970 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -485,7 +485,7 @@ UPDATE OF <replaceable>column_name1</replaceable> [, <replaceable>column_name2</ to change even when the trigger is not fired, because changes made to the row's contents by <literal>BEFORE UPDATE</literal> triggers are not considered. Conversely, a command such as <literal>UPDATE ... SET x = x ...</literal> - will fire a trigger on column <literal>x</literal>, even though the column's + will fire a trigger on column <structfield>x</structfield>, even though the column's value did not change. </para> @@ -598,7 +598,7 @@ UPDATE OF <replaceable>column_name1</replaceable> [, <replaceable>column_name2</ <para> Execute the function <function>check_account_update</function> whenever - a row of the table <literal>accounts</literal> is about to be updated: + a row of the table <structname>accounts</structname> is about to be updated: <programlisting> CREATE TRIGGER check_update @@ -608,7 +608,7 @@ CREATE TRIGGER check_update </programlisting> Modify that trigger definition to only execute the function if - column <literal>balance</literal> is specified as a target in + column <structfield>balance</structfield> is specified as a target in the <command>UPDATE</command> command: <programlisting> @@ -618,7 +618,7 @@ CREATE OR REPLACE TRIGGER check_update EXECUTE FUNCTION check_account_update(); </programlisting> - This form only executes the function if column <literal>balance</literal> + This form only executes the function if column <structfield>balance</structfield> has in fact changed value: <programlisting> @@ -629,7 +629,7 @@ CREATE TRIGGER check_update EXECUTE FUNCTION check_account_update(); </programlisting> - Call a function to log updates of <literal>accounts</literal>, but only if + Call a function to log updates of <structname>accounts</structname>, but only if something changed: <programlisting> |
