database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Doc: use "an SQL" consistently rather than "a SQL"

Browse Source 
Similarly to what was done in 04539e73f, we standardized on SQL being
pronounced "es-que-ell" rather than "sequel" in our documentation.

Two inconsistencies have crept in during the v15 cycle.  The others
existed before but were missed in 04539e73f due to none of the searches
accounting for "SQL" being wrapped in tags.

As with 04539e73f, we don't touch code comments here in order to not
create unnecessary back-patching pain.

Discussion: https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw%40mail.gmail.com
This commit is contained in:
David Rowley 2022-04-20 15:17:56 +12:00
parent 344a225cb9
commit 7bdd489d3d
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/func.sgml
View File

@ -19007,7 +19007,7 @@ SELECT JSON_VALUE(jsonb '[1,2]', 'strict $[*]' DEFAULT 1 ON ERROR);
<listitem>
<para>
Defines whether to wrap a returned sequence of <acronym>SQL/JSON</acronym>
items into a <acronym>SQL/JSON</acronym> array.
items into an <acronym>SQL/JSON</acronym> array.
</para>
<variablelist>
<varlistentry>
@ -19819,7 +19819,7 @@ JSON_SERIALIZE (
<title>Description</title>
<para>
The <function>JSON_SERIALIZE</function> function transforms a SQL/JSON value
The <function>JSON_SERIALIZE</function> function transforms an SQL/JSON value
into a character or binary string.
</para>
</sect5>

2
doc/src/sgml/ref/select.sgml
View File

@ -1715,7 +1715,7 @@ SELECT * FROM (SELECT * FROM mytable FOR UPDATE) ss ORDER BY column1;
<para>
At the <literal>REPEATABLE READ</literal> or <literal>SERIALIZABLE</literal>
transaction isolation level this would cause a serialization failure (with
a <literal>SQLSTATE</literal> of <literal>'40001'</literal>), so there is
an <literal>SQLSTATE</literal> of <literal>'40001'</literal>), so there is
no possibility of receiving rows out of order under these isolation levels.
</para>
</caution>

2
doc/src/sgml/xfunc.sgml
View File

@ -445,7 +445,7 @@ $$ LANGUAGE SQL;
<para>
If the final <literal>SELECT</literal> or <literal>RETURNING</literal>
clause in a <acronym>SQL</acronym> function does not return exactly
clause in an <acronym>SQL</acronym> function does not return exactly
the function's declared result
type, <productname>PostgreSQL</productname> will automatically cast
the value to the required type, if that is possible with an implicit