Bad Timestamp Format at 23 in ...

please display the SQL or Java Statement which constructs the incorrect date

thanks,
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.

Date: Wed, 17 Sep 2008 18:27:40 -0700
From: warren@clarksnutrition.com
To: pgsql-general@postgresql.org
Subject: [GENERAL] Bad Timestamp Format at 23 in ...

I have Postgresql 8.3 (PostgresPlus) running on an Apple with Tomcat 6.
I am using the postgresql-8.3-603.jdbc3.jar driver. My app runs fine
when on the apple, but when I move it over to a Windows machine running
Tomcat 6 that accesses the same exact database on the Apple I get a "Bad
Timestamp Format at 23 in 2008-09-16 18:41:00.479" error. I am guessing
that it has something to do with how Java creates Dates on Unix verses
Windows. Is this a JDBC issue or is there something I need to do in
Postgres to make this work?

--
Thanks,

Warren Bell
909-645-8864
warren@clarksnutrition.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

_________________________________________________________________
Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008

When I insert a record from the Apple app the java date inserted looks
like "2008-09-17 19:52:41.584" and ends up in he db the same way. When I
insert a record from the Windows app the java date inserted looks like
this "2008-09-17 19:55:44.774" and ends up in the db like this
"2008-09-17 19:55:44.77" loosing the last decimal place of precision. My
app gets the "Bad Timestamp" error when it is on Windows and trys to
read the timestamp that is in miiliseconds vs the timestamp that is in
hundredths of seconds.

Martin Gainty wrote:

please display the SQL or Java Statement which constructs the
incorrect date

thanks,
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained
within this transmission.

Date: Wed, 17 Sep 2008 18:27:40 -0700
From: warren@clarksnutrition.com
To: pgsql-general@postgresql.org
Subject: [GENERAL] Bad Timestamp Format at 23 in ...

I have Postgresql 8.3 (PostgresPlus) running on an Apple with Tomcat 6.
I am using the postgresql-8.3-603.jdbc3.jar driver. My app runs fine
when on the apple, but when I move it over to a Windows machine running
Tomcat 6 that accesses the same exact database on the Apple I get a

"Bad

Timestamp Format at 23 in 2008-09-16 18:41:00.479" error. I am guessing
that it has something to do with how Java creates Dates on Unix verses
Windows. Is this a JDBC issue or is there something I need to do in
Postgres to make this work?

--
Thanks,

Warren Bell
909-645-8864
warren@clarksnutrition.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

------------------------------------------------------------------------
Want to do more with Windows Live? Learn �10 hidden secrets� from
Jamie. Learn Now
<http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns%21550F681DAD532637%215295.entry?ocid=TXT_TAGLM_WL_domore_092008&gt;

--
Thanks,

Warren Bell
909-645-8864
warren@clarksnutrition.com