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

Re: BUG #4849: intermittent future timestamps

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David Leppik" <dleppik(at)vocalabs(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4849: intermittent future timestamps
Date: 2009-06-10 18:00:46
Message-ID: 4A2FAE7E0200002500027807@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
David Leppik <dleppik(at)vocalabs(dot)com> wrote: 
> Never mind.  Turns out the bug was in our own code (read:  me,  
> personally, being stupid) to convert a java.sql.Timestamp to  
> java.sql.Date.  Why it works at all in MySQL... I don't even want
> to know.
 
java.sql.Date or java.util.Date?  (You don't show your imports, so
it's impossible to tell from the code snippet.)  If it's
java.util.Date, I can't immediately see why your errors would be
greater than one second.  If it's java.sql.Date, you're probably in
territory where the behavior is undefined, but it's hard to see where
you would get the results you showed.  Perhaps there's an opportunity
for us to make the PostgreSQL JDBC driver behave more sanely in this
circumstance?
 
> Why is it we can spend weeks looking at a bug, and we can't find
> it until we decide to blame it on someone else?
 
It's probably a corollary to the tendency to see our own gaffs when
reading the post coming back from the list much more clearly than they
appeared before clicking "send".  :-/
 
-Kevin

In response to

Responses

pgsql-bugs by date

Next:From: David LeppikDate: 2009-06-10 18:17:43
Subject: Re: BUG #4849: intermittent future timestamps
Previous:From: Tom LaneDate: 2009-06-10 17:16:19
Subject: Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7

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