From: | "John Pagakis" <thebfh(at)toolsmythe(dot)com> |
---|---|
To: | "Kris Jurka" <books(at)ejurka(dot)com> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Issue with now() within a transaction in pg74.213.jdbc.jar |
Date: | 2004-07-02 06:17:04 |
Message-ID: | KKEBKDPPLALEFHBEAOCCAELODPAA.thebfh@toolsmythe.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kris (sorry for the second copy; forgot to cc pgsql-jdbc(at)postgresql(dot)org with
this) -
That did it. Thanks so much!!
Odd though. There seems to be a bug in the cygwin implementation of
postgres. Tim McAuley ran into the same problem I did and posted here:
http://groups.google.com/groups?q=cast+timeofday+timestamp&hl=en&lr=&ie=UTF-
8&selm=bgdif2%2414kk%241%40FreeBSD.csie.NCTU.edu.tw&rnum=5
To save you from having to follow the link - an attempt to cast TIMEOFDAY()
to TIMESTAMP in cygwin's implementation results in:
ERROR: Bad timestamp external representation 'Thu Jul 01 22:29:25.402375
2004 USMST'
Here's what I did to get around it. Perhaps someone out there has a more
elegant solution (and if so I'm all ears because I hate this hack):
SELECT CAST( SUBSTRING( TIMEOFDAY() FROM 1 FOR 31 ) AS TIMESTAMP );
It looks like the CAST problem is a cygwin-only issue.
Thanks again Kris!!
__________________________________________________________________
John Pagakis
Email: ih8spam_thebfh(at)toolsmythe(dot)com
remove the ih8spam_ and you'll find me
"Think enough and you won't know anything."
-- Kenneth Patchen
This signature generated by
... and I Quote!!(tm) Copyright (c) 1999 SpaZmodic Frog Software, Inc.
www.spazmodicfrog.com
-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Kris Jurka
Sent: Thursday, July 01, 2004 4:58 PM
To: John Pagakis
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Issue with now() within a transaction in
pg74.213.jdbc.jar
On Thu, 1 Jul 2004, John Pagakis wrote:
> Most of my tables have a last update date and during some testing in
> Postgres 7.4.1 I noticed that the last_update date was slightly in the
past
> for anything updated within a transaction. The amount it is off by seems
to
> vary: as little as 30 seconds; as much as a couple of minutes.
>
This is not a JDBC issue. now() always returns the time from the start of
the transaction. If you want current wall clock time use timeofday().
Kris Jurka
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Guido Fiala | 2004-07-02 07:11:13 | Re: Query was cancelled - reason? |
Previous Message | Christopher Farley | 2004-07-02 05:11:20 | Re: Puzzling Unix CLASSPATH issue... |