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

Re: [BUG?] Extreme dates

From: Kris Jurka <books(at)ejurka(dot)com>
To: ow <oneway_111(at)yahoo(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [BUG?] Extreme dates
Date: 2004-05-17 20:45:12
Message-ID: Pine.BSO.4.56.0405171540050.24398@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Mon, 17 May 2004, ow wrote:

> [timestamps like 0002-10-30 are incorrectly seen as 2030-02-10].

Yes, that's a bug alright.  I've fixed this in both the stable and 
development cvs trees.  While looking at this I noticed that the timestamp 
code has no provisions for BC dates, so if you're working with years in 
that area, that's something to be aware of.  Fixing that has gone on the 
todo list, but I wanted to get this fix out to you now.

Kris Jurka


In response to

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-05-17 21:10:19
Subject: Re: v3proto Parse/Bind and the query planner
Previous:From: LSanchezDate: 2004-05-17 20:40:10
Subject: Java Test Harness

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