Re: BUG #2885: to_char function - Mailing list pgsql-bugs

From Jorge Godoy
Subject Re: BUG #2885: to_char function
Date
Msg-id 874pqw5jj3.fsf@gmail.com
Whole thread Raw
In response to Re: BUG #2885: to_char function  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane <tgl@sss.pgh.pa.us> writes:

> If we make CC treat 2000 as being in the 20th century, what should YY
> do?

Report "00", IMVHO.  There's no year "0" so year 1 AD is "CC=1, YY=1".  Year
100 is "CC=1, YY=00", year 1000 is "CC=10, YY=00", year 2000 is "CC=20, YY=00"
(1900 is "CC=19, YY=00").  Centuries change on years ending with '01', years
ending with '00' are from the previous century :-)

But for millenia the thing is diffent... ;-)  (Just to complicate a bit more)

> Perhaps more to the point, how do these things act in Oracle?
> to_char is basically an Oracle-compatibility function so we should
> adopt their bugs :-(

I can't answer that...  But my expectations are like Akio's.

--
Jorge Godoy      <jgodoy@gmail.com>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2885: to_char function
Next
From: "David"
Date:
Subject: BUG #2889: Syntax error: WHERE ANY(arrayfield) = N