diff options
| author | Peter Eisentraut | 2017-11-23 14:39:47 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2017-11-23 14:44:28 +0000 |
| commit | 3c49c6facb22cdea979f5d1465ba53f972d32163 (patch) | |
| tree | a7da6a95fdb79a3fa313fb74afda16b746f8704e /doc/src/sgml/rules.sgml | |
| parent | 2f8d6369e60a244f28e0c93b8a02e73758322915 (diff) | |
Convert documentation to DocBook XML
Since some preparation work had already been done, the only source
changes left were changing empty-element tags like <xref linkend="foo">
to <xref linkend="foo"/>, and changing the DOCTYPE.
The source files are still named *.sgml, but they are actually XML files
now. Renaming could be considered later.
In the build system, the intermediate step to convert from SGML to XML
is removed. Everything is build straight from the source files again.
The OpenSP (or the old SP) package is no longer needed.
The documentation toolchain instructions are updated and are much
simpler now.
Peter Eisentraut, Alexander Lakhin, Jürgen Purtz
Diffstat (limited to 'doc/src/sgml/rules.sgml')
| -rw-r--r-- | doc/src/sgml/rules.sgml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 819f2a82946..2074fcca8ea 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -29,8 +29,8 @@ execution. It is very powerful, and can be used for many things such as query language procedures, views, and versions. The theoretical foundations and the power of this rule system are - also discussed in <xref linkend="ston90b"> and <xref - linkend="ong90">. + also discussed in <xref linkend="ston90b"/> and <xref + linkend="ong90"/>. </para> <sect1 id="querytree"> @@ -172,7 +172,7 @@ to allow the executor to find the row to be deleted. (<acronym>CTID</acronym> is added when the result relation is an ordinary table. If it is a view, a whole-row variable is added instead, - as described in <xref linkend="rules-views-update">.) + as described in <xref linkend="rules-views-update"/>.) </para> <para> @@ -823,7 +823,7 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a; the base relation in the appropriate way. Views that are <quote>simple enough</quote> for this are called <firstterm>automatically updatable</firstterm>. For detailed information on the kinds of view that can - be automatically updated, see <xref linkend="sql-createview">. + be automatically updated, see <xref linkend="sql-createview"/>. </para> <para> @@ -862,7 +862,7 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a; <command>UPDATE</command>, and <command>DELETE</command> commands on a view. These rules will rewrite the command, typically into a command that updates one or more tables, rather than views. That is the topic - of <xref linkend="rules-update">. + of <xref linkend="rules-update"/>. </para> <para> |