mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Fix to_date to behave reasonably when CC and YY fields are both used.
Karel Zak
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.234.4.3 2005/01/28 23:13:26 tgl Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.234.4.4 2005/03/25 16:08:49 tgl Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -4458,6 +4458,17 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
In conversions from string to <type>timestamp</type> or
|
||||
<type>date</type>, the <literal>CC</literal> field is ignored if there
|
||||
is a <literal>YYY</literal>, <literal>YYYY</literal> or
|
||||
<literal>Y,YYY</literal> field. If <literal>CC</literal> is used with
|
||||
<literal>YY</literal> or <literal>Y</literal> then the year is computed
|
||||
as <literal>(CC-1)*100+YY</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Millisecond (<literal>MS</literal>) and microsecond (<literal>US</literal>)
|
||||
|
Reference in New Issue
Block a user