| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
| Cc: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ERROR: functions in index expression must be marked IMMUTABLE |
| Date: | 2017-03-03 12:58:02 |
| Message-ID: | CAEzk6ffDTPdbNO3eLGpLBw22wOKF_spe1kLfNL-0URZPTLpjew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3 March 2017 at 12:17, Sven R. Kunze <srkunze(at)mail(dot)de> wrote:
> On 03.03.2017 11:43, Geoff Winkless wrote:
>
> One alternative would be to make to_date accept all language variants of
> months simultaneously. A quick search of google suggests that there aren't
> any overlaps between languages (ie where one language uses "Foo" for March
> and another uses "Foo" for May), although you would have to do some more
> intense research to be sure. As far as I can see there's no other reason
> why to_date would need to be marked as stable/volatile, is there?
>
>
> it seems there are overlapping short months:
>
Trust the Balkan states to find something to disagree over :)
Oh well, that scrubs that idea then.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artur Zakirov | 2017-03-03 13:08:19 | Re: Full Text Search combined with Fuzzy |
| Previous Message | Nicolas Paris | 2017-03-03 12:49:05 | Re: Full Text Search combined with Fuzzy |