Search Postgresql Archives

Re: DATE type output does not follow datestyle parameter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: "Adrian Klaver" <adrian.klaver@xxxxxxxxx>
Actually the relevant code seems to be here:

/src/ backend/parser/gram.y


CURRENT_DATE
                               {
                                       /*
* Translate as "'now'::text::date".
                                        *
....

CURRENT_TIMESTAMP
                               {
                                       /*
                                        * Translate as "now()", since
we have a function that
                                        * does exactly what is needed.
...


Also from :

8.5.1.4. Special Values

The following SQL-compatible functions can also be used to obtain the
current time value for the corresponding data type: CURRENT_DATE,
CURRENT_TIME, CURRENT_TIMESTAMP, LOCALTIME, LOCALTIMESTAMP. The latter
four accept an optional subsecond precision specification. (See Section
9.9.4.) Note that these are SQL functions and are not recognized in data
input strings.



It would seem the functions are special cased.


As below, normal DATE constants also does not follow the setting of datestyle. Is this a bug?

SET datestyle = 'Postgres, MDY';
SELECT DATE 'Jan 2 2013';
   date
------------
01-02-2013
(1 row)

Regards
MauMau



--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux