1
0
mirror of https://github.com/postgres/postgres.git synced 2025-10-19 15:49:24 +03:00
Files
postgres/doc/src/sgml
Robert Haas 4a66300acd Allow db.schema.table patterns, but complain about random garbage.
psql, pg_dump, and pg_amcheck share code to process object name
patterns like 'foo*.bar*' to match all tables with names starting in
'bar' that are in schemas starting with 'foo'. Before v14, any number
of extra name parts were silently ignored, so a command line '\d
foo.bar.baz.bletch.quux' was interpreted as '\d bletch.quux'.  In v14,
as a result of commit 2c8726c4b0, we
instead treated this as a request for table quux in a schema named
'foo.bar.baz.bletch'. That caused problems for people like Justin
Pryzby who were accustomed to copying strings of the form
db.schema.table from messages generated by PostgreSQL itself and using
them as arguments to \d.

Accordingly, revise things so that if an object name pattern contains
more parts than we're expecting, we throw an error, unless there's
exactly one extra part and it matches the current database name.
That way, thisdb.myschema.mytable is accepted as meaning just
myschema.mytable, but otherdb.myschema.mytable is an error, and so
is some.random.garbage.myschema.mytable.

Mark Dilger, per report from Justin Pryzby and discussion among
various people.

Discussion: https://www.postgresql.org/message-id/20211013165426.GD27491%40telsasoft.com
2022-04-20 11:39:44 -04:00
..
2021-11-24 18:34:30 +02:00
2020-07-05 15:37:57 +02:00
2021-07-16 12:39:23 +02:00
2020-10-26 19:17:05 -04:00
2021-09-29 11:56:36 +09:00
2021-09-29 11:56:36 +09:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2021-01-29 14:09:41 +13:00
2021-09-26 19:18:23 +09:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2021-12-09 15:20:45 +09:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2021-07-05 09:38:17 +05:30
2020-07-18 22:43:35 +09:00
2021-07-05 09:38:17 +05:30
2022-01-02 17:06:32 +01:00
2021-07-16 12:39:23 +02:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2021-07-16 12:39:23 +02:00
2022-01-07 19:04:56 -05:00
2021-09-19 11:36:53 -04:00
2021-07-16 12:39:23 +02:00
2021-01-05 14:26:37 -05:00
2020-08-28 08:19:12 +02:00
2022-01-25 10:49:30 +09:00
2021-07-16 12:39:23 +02:00
2020-12-23 09:33:20 -05:00
2021-07-05 09:38:17 +05:30
2022-01-25 10:49:30 +09:00
2020-06-07 17:16:30 -04:00
2021-09-29 11:56:36 +09:00
2021-07-16 12:39:23 +02:00
2021-12-08 16:54:53 -05: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.