Amit Kelkar ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Concurrent JDBC connections to result in wrong data
Long Description
We are designing a major enterprise resource management system for a client and are
using java (s
Ok, I now understand more about how Postgres handles these older dates but
we're still seeing a problem that I'm not sure how to handle. Simply put, we
write a TIMESTAMP via JDBC and then read it back. What we write and what we
read are different. The only way I can think of fixing the problem is
Patch reversed. Please advise how to continue.
> Please pull this patch. It breaks JDBC1 support. The JDBC1 code no
> longer compiles, due to objects being referenced in this patch that do
> not exist in JDK1.1.
>
> thanks,
> --Barry
>
>
> [copy] Copying 1 file to
> /home/blind/te
