Peter Eisentraut 7844c9918a psql: Show all query results by default
Previously, psql printed only the last result if a command string
returned multiple result sets.  Now it prints all of them.  The
previous behavior can be obtained by setting the psql variable
SHOW_ALL_RESULTS to off.

This is a significantly enhanced version of
3a5130672296ed4e682403a77a9a3ad3d21cef75 (that was later reverted).
There is also much more test coverage for various psql features now.

Author: Fabien COELHO <coelho@cri.ensmp.fr>
Reviewed-by: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Reviewed-by: "Iwata, Aya" <iwata.aya@jp.fujitsu.com> (earlier version)
Reviewed-by: Daniel Verite <daniel@manitou-mail.org> (earlier version)
Reviewed-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com> (earlier version)
Reviewed-by: vignesh C <vignesh21@gmail.com> (earlier version)
Discussion: https://www.postgresql.org/message-id/flat/alpine.DEB.2.21.1904132231510.8961@lancre
2022-04-04 20:00:33 +02:00
..
2022-03-30 16:30:37 -04:00
2021-11-24 18:32:56 +02:00
2020-07-05 15:37:57 +02:00
2020-10-26 19:17:05 -04:00
2021-09-29 11:56:13 +09:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2022-03-31 01:13:33 +02:00
2018-10-11 11:43:56 -07:00
2021-12-13 17:33:32 -05:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2022-01-20 09:01:12 -05:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2022-03-30 20:16:23 +02:00
2017-10-17 15:10:33 -04:00
2020-07-18 22:43:35 +09:00
2019-10-25 20:39:41 +02:00
2017-10-17 15:10:33 -04:00
2017-10-17 15:10:33 -04:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2022-01-07 19:04:57 -05:00
2019-09-08 10:27:29 +02:00
2021-08-27 18:20:40 +02:00
2022-03-28 16:47:48 +02:00
2021-01-05 14:26:37 -05:00
2020-08-28 08:19:12 +02:00
2020-12-23 09:33:20 -05:00
2022-03-28 16:47:48 +02:00
2021-06-28 11:31:16 -04:00
2021-06-28 11:31:16 -04:00
2019-09-08 10:27:29 +02:00
2021-09-29 11:56:13 +09:00
2022-02-15 11:13:49 +01:00
2022-03-28 16:47:48 +02:00
2022-02-03 14:05:02 -05:00
2021-12-08 16:54:52 -05:00
2019-09-08 10:27:29 +02:00

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

Linking within DocBook 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

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

<link>
	use to supply text for the link, only uses linkend, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html
	can be embedded inside of <command>, unlike <xref>


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
----------

- For an internal link, if you want to supply text, use <link>, else
  <xref>.

- Specific nouns like GUC variables, SQL commands, and contrib modules
  usually have xreflabels.

- For an external link, use <ulink>, with or without link text.

- xreflabels added to tags prevent the chapter/section for id's from being
  referenced;  only the xreflabel is accessible.  Therefore, use xreflabels
  only when linking is common, and chapter/section information is unneeded.