Re:   The jdbc - Mailing list pgsql-general

From stevegy@126.com
Subject Re:   The jdbc
Date
Msg-id 45B5B4E3.000010.14125@bj126app65.126.com
Whole thread Raw
In response to Re: The jdbc and current_timestamp  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,
 
I found the point. The auto_commit flag and jdbc connection pool is some of problem and the current_timestamp is not a now() meanful function. I have to use the CAST(timeofday() as timestamp) to.
 
Thanks.
 
Regards, Steve Yao
 
 
 

在2007-01-17,"Tom Lane" 写道:
Richard Huxton <dev@archonet.com> writes:
> The time is fixed at the start of the transaction. This lets you do
> several inserts having the same timestamp.

I think there's another problem here, which is that he's declared
"currenttime" as a timestamp without time zone, but the
CURRENT_TIMESTAMP function yields timestamp with time zone,
meaning there's a TimeZone-dependent conversion going on.  It sounds
to me like there's a difference between the TimeZone setting between
his web app and his psql, leading to an hour's offset, plus a smaller
offset having to do with time-since-transaction-start.

> See here for details of timeofday() etc.
> http://www.postgresql.org/docs/8.2/static/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT

And read the preceding chapter's discussion of the different datetime
data types.
		regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend



独家!网易3G免费邮,还赠送280兆网盘 www.126.com

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Regular expressions and arrays and ANY() question
Next
From: "Shoaib Mir"
Date:
Subject: Re: MSSQL/ASP migration