RE: JDBC and Timestamps
От | Peter Mount |
---|---|
Тема | RE: JDBC and Timestamps |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B1E4@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответ на | JDBC and Timestamps (Chris Ryan <chris@greatbridge.com>) |
Список | pgsql-interfaces |
This should already be fixed in cvs. Peter -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council -----Original Message----- From: Chris Ryan [mailto:chris@greatbridge.com] Sent: Saturday, August 05, 2000 1:26 PM To: pgsql-interfaces@postgresql.org Subject: [INTERFACES] JDBC and Timestamps I'm working on a project where I update/insert/select records through JDBC and I'm noticing problems with the timestamp fields. The JDBC driver when writing a Timestamp value to postgres is passing the value to the backend as a String in the following format "yyyy-mm-dd hh:mm:ss.fffffffff" <-- the last part .fffffffff is nanosecs. When Postgres reads this is things it is millisecs so converts it and appends the timezone. Now when the JDBC driver reads the value back in it is trying to do a date conversion from a string using the format "yyyy-mm-dd hh:mm:sszzz" which has timezone but no millisecs. The different formats of course cause exceptions to be generated. I tried using the setLenient(true) but this didn't make any difference. Chris Ryan
В списке pgsql-interfaces по дате отправления: