From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> |
Cc: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: to_char and i18n |
Date: | 2005-12-22 04:28:18 |
Message-ID: | 18904.1135225698@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> writes:
> (Some time ago I proposed an--incomplete--patch and it was rejectd by
> Karel arguing that to_char functions should behave *exactly* the same
> way that they do in Oracle.)
That is the accepted plan for to_char ... of course, if Oracle changes
to_char every so often, it'll get more interesting to decide what to do.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2005-12-22 04:37:52 | Re: to_char and i18n |
Previous Message | Manuel Sugawara | 2005-12-22 04:20:05 | Re: to_char and i18n |
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2005-12-22 04:37:52 | Re: to_char and i18n |
Previous Message | Manuel Sugawara | 2005-12-22 04:20:05 | Re: to_char and i18n |