Re: [BUGS] IYYY: unexpected behaviour

#1

Zubkovsky, Sergey wrote:

Quote:

SELECT to_char( '2006-01-01'::timestamp, 'IYYY-MM-DD' ) AS strange,
to_char( '2006-01-02'::timestamp, 'IYYY-MM-DD' ),
to_char( '2006-01-01'::timestamp, 'YYYY-MM-DD' );

does produce unexpected result for column 'strange':

strange | to_char | to_char
------------+------------+------------
2005-01-01 | 2006-01-02 | 2006-01-01

This is correct. January 1, 2006 belongs to 2005 in this "ISO" way of
counting.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [BUGS] IYYY: unexpected behaviour

mailing.database.pgsql-bugs mailing.database.pgsql-bugs

Re: [BUGS] IYYY: unexpected behaviour - 10-12-2006 , 12:02 PM