database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-04 20:11:56 +03:00
Code Activity

doc: add commas after 'i.e.' and 'e.g.'

Browse Source 
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.

Discussion: https://postgr.es/m/20200825183619.GA22369@momjian.us

Backpatch-through: 9.5
This commit is contained in:
Bruce Momjian
2020-08-31 18:33:37 -04:00
parent 50ed605b3e
commit 953c64e0f6
46 changed files with 103 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/create_table.sgml
View File

@@ -914,7 +914,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
one or more columns on which the uniqueness is not enforced.
Note that although the constraint is not enforced on the included columns,
it still depends on them. Consequently, some operations on these columns
(e.g. <literal>DROP COLUMN</literal>) can cause cascaded constraint and
(e.g., <literal>DROP COLUMN</literal>) can cause cascaded constraint and
index deletion.
</para>
</listitem>
@@ -960,7 +960,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
of columns to be specified which will be included in the non-key portion
of the index. Although uniqueness is not enforced on the included columns,
the constraint still depends on them. Consequently, some operations on the
included columns (e.g. <literal>DROP COLUMN</literal>) can cause cascaded
included columns (e.g., <literal>DROP COLUMN</literal>) can cause cascaded
constraint and index deletion.
</para>
</listitem>