database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

docs: HTML-escape '>' in '=>' using HTML entities

Browse Source
This commit is contained in:
Bruce Momjian
2015-08-05 23:03:45 -04:00
parent b8fe12a836
commit e641d7b22f
10 changed files with 34 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/syntax.sgml
View File

@ -2592,10 +2592,10 @@ SELECT concat_lower_or_upper('Hello', 'World');
<para>
In named notation, each argument's name is specified using
<literal>=></literal> to separate it from the argument expression.
<literal>=&gt;</literal> to separate it from the argument expression.
For example:
<screen>
SELECT concat_lower_or_upper(a => 'Hello', b => 'World');
SELECT concat_lower_or_upper(a =&gt; 'Hello', b =&gt; 'World');
concat_lower_or_upper
-----------------------
hello world
@ -2606,13 +2606,13 @@ SELECT concat_lower_or_upper(a => 'Hello', b => 'World');
using named notation is that the arguments may be specified in any
order, for example:
<screen>
SELECT concat_lower_or_upper(a => 'Hello', b => 'World', uppercase => true);
SELECT concat_lower_or_upper(a =&gt; 'Hello', b =&gt; 'World', uppercase =&gt; true);
concat_lower_or_upper
-----------------------
HELLO WORLD
(1 row)
SELECT concat_lower_or_upper(a => 'Hello', uppercase => true, b => 'World');
SELECT concat_lower_or_upper(a =&gt; 'Hello', uppercase =&gt; true, b =&gt; 'World');
concat_lower_or_upper
-----------------------
HELLO WORLD
@ -2645,7 +2645,7 @@ SELECT concat_lower_or_upper(a => 'Hello', uppercase => true, b => 'World');
already mentioned, named arguments cannot precede positional arguments.
For example:
<screen>
SELECT concat_lower_or_upper('Hello', 'World', uppercase => true);
SELECT concat_lower_or_upper('Hello', 'World', uppercase =&gt; true);
concat_lower_or_upper
-----------------------
HELLO WORLD