Skip site navigation (1) Skip section navigation (2)

Re: Bug in to_timestamp()

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org>, Gqms2 Galway <gqms2(at)nortelnetworks(dot)com>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgreSQL(dot)org>
Subject: Re: Bug in to_timestamp()
Date: 2000-08-17 10:47:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
On Wed, 16 Aug 2000, Gqms2 Galway wrote:

> Please enter a FULL description of your problem:
> ------------------------------------------------
> The to_timestamp function is not working as per the documentation. See the
> examples below.

 No. It is not bug. Where is in a documentation your example?

 Instead this, in the documentation is next:

	YYYY = year (4 or more digits)

 Timestamp range is 4714 BC -- 1465001 AC.

> select to_timestamp('20000816000001', 'YYYYMMDDHH24MISS') returns
> '30/12/1899' (wrong)

 The PostgreSQL hasn't directly limited year. The to_timestamp() stop 
parse YYYY at first non-digit char.  

> select to_timestamp('2000 0816000001', 'YYYY MMDDHH24MISS')  returns
> '16/08/2000 00:00:01' (ok)

Yes, it's right.

 If you want store full timestamp into one big number is better year
keep to end of this number, like:

test=# select to_timestamp('08160000012000', 'MMDDHH24MISSYYYY');
 2000-08-16 00:00:01+02

 And YYY, YY, Y ... it's *hell*, and we support it because Oracle has it 
too. How number you want create from:
	'01' -- 'YY' --->  2001, 1901 or 0001 .. grrrr

 to_timestamp() use last possibility.

Some commets/suggestions about greater years than 9999 in 
to_timestamp() / to_date()?


In response to

pgsql-hackers by date

Next:From: Karel ZakDate: 2000-08-17 11:17:50
Subject: right RULE?
Previous:From: Patrick WelcheDate: 2000-08-17 10:46:56
Subject: Re: Regression Tests

pgsql-bugs by date

Next:From: Bob RivoirDate: 2000-08-18 02:32:41
Previous:From: Stephan SzaboDate: 2000-08-17 06:19:20
Subject: Re: [BUGS] help me

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group