"" 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
On 02/06/11 10:53, wcting...@163.com wrote:
> but, what about "prepare p1 as select 'today'::timestamp"??
> today() is not a builtin function, we can't change it to "select
> today()::timestamp";
The keyword-to-timestamp conversions are ugly historical hacks.
Use the SQL-standard current_date, cu
The following bug has been logged online:
Bug reference: 6047
Logged by:
Email address: wcting...@163.com
PostgreSQL version: 9.0.4
Operating system: WinXP 32bit
Description:prepare p1 as select 'now'::timestamp; then "execute p1"
many times, they return the same tim
