Thread: strange JDBC error
I'm getting some bizarre JDBC errors. I just started at a new job and my colleagues are all using the PostgreSQL RPMs, but I compiled it from source. I am the only one getting this error, and I would really like to figure it out... =) [20/07/2000 17:05:39:989 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Formatat 0 in 2000-07-19 17:55:50.59-07 *** [20/07/2000 17:06:07:725 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Formatat 0 in 2000-07-19 17:55:50.59-07 *** [20/07/2000 17:07:46:413 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Formatat 0 in 2000-07-19 17:55:50.59-07 *** [20/07/2000 17:07:48:722 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Formatat 0 in 2000-07-19 17:55:50.59-07 *** [20/07/2000 17:07:48:870 PDT] *** WGException thrown: Error creating membership for group 1 and username vsync from editinput params: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 -- Tim Howe Associate Software Engineer Wego Inc. -- wego.com
Tim Howe <vsync@wego.com> writes: > I'm getting some bizarre JDBC errors. I just started at a new job and > my colleagues are all using the PostgreSQL RPMs, but I compiled it > from source. I am the only one getting this error, and I would really > like to figure it out... =) > > [20/07/2000 17:05:39:989 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Formatat 0 in 2000-07-19 17:55:50.59-07 Never mind, I figured it out. Apparently PostgreSQL itself was updated to support 100ths of a second in timestamps, but the JDBC driver was not. I updated and tested the driver, and it seems to work fine now. Patch attached. -- Tim Howe Associate Software Engineer Wego Inc. -- wego.com
Attachment
getTimestamp() has always given us some problems. As you compiled from source, try getting the current cvs repository. There's a couple of bug fixes, including the current getTimestamp() fix. Peter -- Peter T Mount peter@retep.org.uk, peter@retepdigital.com, me@petermount.com Homepage: http://www.retep.org.uk Contact details @ http://petermount.com PostgreSQL JDBC: http://www.retep.org.uk/postgres/ Java PDF generator: http://www.retep.org.uk/pdf/ ----- Original Message ----- From: Tim Howe <vsync@wego.com> To: <pgsql-general@postgresql.org> Sent: Friday, July 21, 2000 1:35 AM Subject: [GENERAL] strange JDBC error > I'm getting some bizarre JDBC errors. I just started at a new job and > my colleagues are all using the PostgreSQL RPMs, but I compiled it > from source. I am the only one getting this error, and I would really > like to figure it out... =) > > [20/07/2000 17:05:39:989 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 > *** > [20/07/2000 17:06:07:725 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 > *** > [20/07/2000 17:07:46:413 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 > *** > [20/07/2000 17:07:48:722 PDT] *** WGException thrown: Error querying membership for group 1 and user 1: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 > *** > [20/07/2000 17:07:48:870 PDT] *** WGException thrown: Error creating membership for group 1 and username vsync from edit input params: Bad Timestamp Format at 0 in 2000-07-19 17:55:50.59-07 > > -- > Tim Howe > Associate Software Engineer > Wego Inc. -- wego.com