1
0
mirror of https://github.com/postgres/postgres.git synced 2025-08-24 09:27:52 +03:00
Files
postgres/doc/src/sgml
Tom Lane 18831346d4 Doc: fix ancient mistake, or at least obsolete info, in rules example.
The example of expansion of multiple views claimed that the resulting
subquery nest would not get fully flattened because of an aggregate
function.  There's no aggregate in the example, though, only a user
defined function confusingly named MIN().  In a modern server, the
reason for the non-flattening is that MIN() is volatile, but I'm
unsure whether that was true back when this text was written.

Let's reduce the confusion level by using LEAST() instead (which
we didn't have at the time this example was created).  And then
we can just say that the planner will flatten the sub-queries, so
the rewrite system doesn't have to.

Noted by Paul Jungwirth.  This text is old enough to vote, so
back-patch to all supported branches.

Discussion: https://postgr.es/m/CA+renyXZFnmp9PcvX1EVR2dR=XG5e6E-AELr8AHCNZ8RYrpnPw@mail.gmail.com
2019-11-11 14:39:55 -05:00
..
2016-08-10 21:39:59 -04:00
2014-05-06 21:28:58 -04:00
2017-03-14 13:45:51 -04:00
2016-07-14 22:28:41 -04:00
2015-09-26 21:02:24 -04:00
2015-09-10 21:40:06 -04:00
2018-06-20 16:07:47 +02:00
2019-10-16 13:10:57 +09:00
2016-01-22 12:29:22 -05:00
2016-05-13 21:25:46 -04:00
2019-08-20 13:46:19 +09:00
2019-01-05 12:49:51 +09:00
2015-08-14 12:10:35 -04:00
2019-01-02 12:44:25 -05:00
2019-08-20 13:46:19 +09:00
2017-11-10 08:32:22 -05:00
2015-09-10 21:40:06 -04:00
2015-04-12 19:07:46 +02:00
2016-12-13 19:14:42 -06:00
2019-01-05 12:49:51 +09:00
2015-08-31 14:07:41 +02:00
2014-05-06 21:28:58 -04:00
2019-08-20 13:46:19 +09:00
2018-03-21 23:11:56 +09:00
2015-04-26 10:33:14 -04:00
2015-09-05 11:36:18 +03:00
2019-08-20 13:46:19 +09:00
2015-06-03 20:19:47 -04:00
2017-03-07 22:46:39 -05:00
2016-05-01 21:34:41 -04:00
2014-08-30 10:52:36 -05:00
2019-08-20 13:46:19 +09:00

<!-- doc/src/sgml/README.links -->

Linking within SGML documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section number from the title of the target
	link, or xreflabel if defined at the target, or refentrytitle if target
        is a refentry;  has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

<link>
	use to supply text for the link, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

o  If you want to supply text, use <link>, else <xref>
o  Do not use text with <ulink> so the URL appears in printed output
o  Specific nouns like GUC variables, SQL commands, and contrib modules
   usually have xreflabels