Commit01ddd2f

committed

doc: Make terminology in glossary consistent

Use "reside in" rather than "belong to" for objects in a schema.Previous use was a mix of the two.Author: Alvaro Herrera <alvherre@alvh.no-ip.org>Discussion:https://www.postgresql.org/message-id/202106021932.idmbjjaqk7ke@alvherre.pgsql

1 parente615988 commit01ddd2fCopy full SHA for 01ddd2f

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1448,7 +1448,7 @@`
`1448`	`1448`	`known as <firstterm>local objects</firstterm>.`
`1449`	`1449`	`</para>`
`1450`	`1450`	`<para>`
`1451`		`- Most local objectsbelong to a specific`
	`1451`	`+ Most local objectsreside in a specific`
`1452`	`1452`	`<glossterm linkend="glossary-schema">schema</glossterm> in their`
`1453`	`1453`	`containing database, such as`
`1454`	`1454`	`<glossterm linkend="glossary-relation">relations</glossterm> (all types),`
`@@ -1458,7 +1458,7 @@`
`1458`	`1458`	`are enforced to be unique.`
`1459`	`1459`	`</para>`
`1460`	`1460`	`<para>`
`1461`		`- There also exist local objects that do notbelong to schemas; some examples are`
	`1461`	`+ There also exist local objects that do notreside in schemas; some examples are`
`1462`	`1462`	`<glossterm linkend="glossary-extension">extensions</glossterm>,`
`1463`	`1463`	`<glossterm linkend="glossary-cast">data type casts</glossterm>, and`
`1464`	`1464`	`<glossterm linkend="glossary-foreign-data-wrapper">foreign data wrappers</glossterm>.`

Comments

(0)