Thread: DateStyle bug

Guys, 

While porting an aplication from 7.0 to 7.2 I found a bug with the use
of DateStyle variable:

masm@dep4$ psql test
test=# set DateStyle to 'European' ;
SET VARIABLE
test=# select now()::date;   now
------------2002-02-21
(1 row)

test=# \c test
You are now connected to database test
test=# set DateStyle to 'Postgres' ;
SET VARIABLE
test=# set DateStyle to 'European' ;
SET VARIABLE
test=# select now()::date;   now
------------21-02-2002
(1 row)

test=# select version();                         version
-----------------------------------------------------------PostgreSQL 7.2 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)


Regards,
Manuel Sugawara.

> While porting an aplication from 7.0 to 7.2 I found a bug with the use
> of DateStyle variable:

No bug that I can see. Please be more specific, or the explanation might
be that you have some (understandable) confusion over output date styles
(e.g. 'Postgres', 'ISO') and style hints for both input and output (e.g.
'European', 'US').

Simply setting 'European' will only affect the order of priorities for
interpreting months and days for input parameters when the style is set
to 'ISO' (which specifies the order of fields for dates and times, so is
fixed for output). When the output style is set to 'Postgres' then
'European' also affects the order of output of months and days.
                     - Thomas

> masm@dep4$ psql test
> test=# set DateStyle to 'European' ;
> SET VARIABLE
> test=# select now()::date;
>     now
> ------------
>  2002-02-21
> (1 row)
> 
> test=# \c test
> You are now connected to database test
> test=# set DateStyle to 'Postgres' ;
> SET VARIABLE
> test=# set DateStyle to 'European' ;
> SET VARIABLE
> test=# select now()::date;
>     now
> ------------
>  21-02-2002
> (1 row)