RE: RE: JDBC Timestamp Problem
От | Peter Mount |
---|---|
Тема | RE: RE: JDBC Timestamp Problem |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B64D@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответ на | JDBC Timestamp Problem (yves@asua.vlaanderen.net) |
Список | pgsql-interfaces |
Yes, about 1-2 months ago ;-) The current CVS has the patch applied. As soon as I get the domain problems sorted, I'm going to tripple check Timestamp as I'd like to see the next release without the timestamp bug reappearing... Peter -- Peter Mount Enterprise Support Officer, Maidstone Borough Council Email: petermount@maidstone.gov.uk WWW: http://www.maidstone.gov.uk All views expressed within this email are not the views of Maidstone Borough Council > -----Original Message----- > From: Ken Kachnowich [mailto:khkachn@madweed.ncsc.mil] > Sent: Monday, December 11, 2000 5:30 PM > To: pgsql-interfaces > Subject: [INTERFACES] RE: JDBC Timestamp Problem > > > I ran into a Timestamp problem a while back. The Postgres back end > seems to return 2 digits for the milliseconds when the JDBC > is expecting > > 3 digits (and 3 digits is correct). > > I am not sure if this has already been fixed or reported or even if it > is the > real problem at all. > > Does anyone know where I could checked to see if a patch is availalbe > for this? > > Thanks, > > Ken > > >
В списке pgsql-interfaces по дате отправления: