Re: BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time
Date
Msg-id 14435.1307023804@sss.pgh.pa.us
Whole thread Raw
In response to BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time  ("" <wcting163@163.com>)
List pgsql-bugs
"" <wcting163@163.com> writes:
> 1). although i kown that, "the system will convert **now** to a timestamp as
> soon as the constant is parsed",
> i think this is a bug.

Sorry, it's not a bug, and we're not going to change it.

> but, what about "prepare p1 as select 'today'::timestamp"??
> today() is not a builtin function, we can't change it to "select
> today()::timestamp";

You can get that by using date_trunc on the result of now(); or there's
current_date, which is actually SQL-standard unlike these other things.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: collation problem on 9.1-beta1
Next
From: Alexey Klyukin
Date:
Subject: Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message