Обсуждение: Bad timestamp external representation
Hi everyone:
I am using Postgresql 7.3.4 and found a problem inserting "Timestamp" objects through
JDBC Prepared Statements when the time zone is set to Canada/Newfoundland (3 hours and
30 minutes from MGT). I am trying to insert "new Timestamp(0L)" into one of the fields.
The database replies with an error message:
JDBC Prepared Statements when the time zone is set to Canada/Newfoundland (3 hours and
30 minutes from MGT). I am trying to insert "new Timestamp(0L)" into one of the fields.
The database replies with an error message:
Bad timestamp external representation '1969-12-31 20:30:00.000000-030-30'
Most likely, the database doesn't understand the last part of the timestamp, which is
'-30' (30 minutes). It works properly only with time zones that don't have that additional
half hour difference.
'-30' (30 minutes). It works properly only with time zones that don't have that additional
half hour difference.
I could not find any useful information regarding that issue.
Any help would be appreciated.
Thanx
On Fri, 19 Mar 2004, Denis Khabas wrote: > Hi everyone: > I am using Postgresql 7.3.4 and found a problem inserting "Timestamp" > objects through JDBC Prepared Statements when the time zone is set to > Canada/Newfoundland (3 hours and 30 minutes from MGT). I am trying to > insert "new Timestamp(0L)" into one of the fields. The database replies > with an error message: > This has been fixed in the 7.4 driver which is compatible with 7.3 servers. Try downloading it from http://jdbc.postgresql.org/download.html Kris Jurka
Denis, This is more appropriate for the jdbc mail list. --Barry Denis Khabas wrote: > Hi everyone: > > I am using Postgresql 7.3.4 and found a problem inserting "Timestamp" objects through > JDBC Prepared Statements when the time zone is set to Canada/Newfoundland (3 hours and > 30 minutes from MGT). I am trying to insert "new Timestamp(0L)" into one of the fields. > The database replies with an error message: > > Bad timestamp external representation '1969-12-31 20:30:00.000000-030-30' > > Most likely, the database doesn't understand the last part of the timestamp, which is > '-30' (30 minutes). It works properly only with time zones that don't have that additional > half hour difference. > > I could not find any useful information regarding that issue. > Any help would be appreciated. > > > Thanx >