| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Boris Kirzner <borisk(at)mainsoft(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Bug in storing Timestamp |
| Date: | 2005-04-14 09:17:42 |
| Message-ID: | Pine.BSO.4.56.0504140407320.17685@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 11 Apr 2005, Boris Kirzner wrote:
> Short description :
> Storing java.sql.Timestamp with specified milliseconds value results to
> wrong value stored in db.
>
> PostgreSQL version : 8.0.1
> Driver version : 8.0 build 310
>
> Detailed description :
> In order to reproduce the bug run the following code.
> Create the table in the db.
> The code creates a timestamp of "0001-01-01 02:02:02.0" and stores it
> into the db.
> The actual value stored is "02:22:42".
I am not able to reproduce this problem. The attached test case shows a
problem with storing java.sql.Time into a timetz type because the correct
offset is not saved, but that's not what you've described. Perhaps it is
something specific to your timezone?
Kris Jurka
| Attachment | Content-Type | Size |
|---|---|---|
| TimeTest.java | text/plain | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-04-14 09:19:02 | Re: Data type for array of byte |
| Previous Message | Kris Jurka | 2005-04-13 23:15:30 | Re: Pam Authentication is supported? |