Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Bad timestamp external representation

From: Barry Lind <blind(at)xythos(dot)com>
To: Denis Khabas <dkhabas(at)bluecatnetworks(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org,postgres jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [HACKERS] Bad timestamp external representation
Date: 2004-03-26 20:06:49
Message-ID: 40648D59.9080609@xythos.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
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
> 


In response to

pgsql-hackers by date

Next:From: Michael BrusserDate: 2004-03-26 20:17:32
Subject: database is shutting down
Previous:From: Tom LaneDate: 2004-03-26 18:42:37
Subject: Re: Per database users/admins, handy for database virtual hosting...

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-03-26 20:36:26
Subject: Re: Bad timestamp external representation
Previous:From: Tom LaneDate: 2004-03-26 02:18:31
Subject: Re: [JDBC] Problem with Serializable transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group