Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 3fce180

Browse files
committed
About section 8.5.1.5. ("Special Values"): I suggest adding LOCALTIMESTAMP and LOCALTIME to the first paragraph. Maybe it should be phrased as: The following SQL-compatible functions can be used to obtain current datetime-related values: CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, LOCALTIME and LOCALTIMESTAMP. (See Section 9.8.4.) Troels Arvin
1 parent 172b125 commit 3fce180

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

doc/src/sgml/datatype.sgml

+7-6
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.124 2003/09/12 22:17:22 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.125 2003/10/09 19:13:48 momjian Exp $
33
-->
44

55
<chapter id="datatype">
@@ -1759,11 +1759,12 @@ January 8 04:05:06 1999 PST
17591759

17601760
<para>
17611761
The following <acronym>SQL</acronym>-compatible functions can be
1762-
used as date or time
1763-
values for the corresponding data type: <literal>CURRENT_DATE</literal>,
1764-
<literal>CURRENT_TIME</literal>,
1765-
<literal>CURRENT_TIMESTAMP</literal>. The latter two accept an
1766-
optional precision specification. (See also <xref linkend="functions-datetime-current">.)
1762+
used as date or time values for the corresponding data type:
1763+
<literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>,
1764+
<literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>,
1765+
<literal>LOCALTIMESTAMP</literal>. The latter four accept an
1766+
optional precision specification. (See also <xref
1767+
linkend="functions-datetime-current">.)
17671768
</para>
17681769

17691770
<para>

0 commit comments

Comments
 (0)