Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
> > That's because a quoted literal isn't necessarily a timestamp. Without
> > context it could be anything, and in the context of comparing to a date
> > the planner probably tries to make it a date.
> I think the real point here is this:
> regression=# select '2008-12-09 02:00:00'::date;
> (1 row)
> ie, when it does decide that a literal should be a date, it will happily
> throw away any additional time-of-day fields that might be in there.
> Had it raised an error, Stefano might have figured out his mistake
> ISTM we deliberately chose this behavior awhile back, but I wonder
> whether it does more harm than good.
Well, it seems fine to me because it works just like the cast of a float
to an integer:
test=> select 1.23432::integer;
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-sql by date
|Next:||From: Pascal Tufenkji||Date: 2008-12-10 14:33:07|
|Subject: Is there a bug in PostgreSQL ?|
|Previous:||From: Allan Kamau||Date: 2008-12-10 12:46:33|
|Subject: Collapsing (select) row values into single text field.|