From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
Cc: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why *exactly* is date_trunc() not immutable ? |
Date: | 2007-02-19 09:04:20 |
Message-ID: | 45D96814.2070702@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Glaesemann wrote:
>
> On Feb 18, 2007, at 20:29 , Karsten Hilbert wrote:
>
>> What I don't understand, however, is exactly *why* date_trunc is not
>> immutable ?
>
> I believe it's because the result of date_trunc depends on the time zone
> setting for the session.
I understand the reasoning, but _under the conditions_ it is being used
by the OP it could have been immutable, right?
The index values will still match up with the queried values if they are
in the same time zone.
I'm not asking to change it back to immutable (it isn't), I just
realized that the stability of functions may actually be conditional.
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2007-02-19 09:10:56 | Re: Why *exactly* is date_trunc() not immutable ? |
Previous Message | Alberto Cabello Sanchez | 2007-02-19 08:52:32 | Postgresql 8.1 y Debian [ Era: Re: postgreSQL ] |