My typo. Converting java.sql.Timestamp to java.util.Date was buggy on
my end.
David
On Jun 10, 2009, at 1:00 PM, Kevin Grittner wrote:
David Leppik 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.D
David Leppik 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,
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.
Why is it we can spend weeks looking at a bug, and we can't find it
until we decide to bla
"David Leppik" writes:
> We are intermittently getting results from now() which are around 10 minutes
> in the future. Most calls return a reasonable value. Because the erroneous
> timestamps are in the future, they cannot be explained by transaction
> delays.
Postgres is just reporting what it
The following bug has been logged online:
Bug reference: 4849
Logged by: David Leppik
Email address: dlep...@vocalabs.com
PostgreSQL version: 8.3.5
Operating system: Linux (CentOS 5.2)
Description:intermittent future timestamps
Details:
We are intermittently getting
