| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: to_char, support for EEEE format |
| Date: | 2009-08-02 16:34:10 |
| Message-ID: | 539.1249230850@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> Tom, please, can you write your opinion on my last proposal - print
> ### with raise warning.
The idea of printing a warning seems completely horrid to me. From a
logical point of view, either we think it's an error or we don't. From
a practical point of view, warnings usually accomplish little except to
bloat log files that a human might or might not ever look at.
The real bottom line for to_char issues is almost always that we should
do what Oracle does. Has anyone checked this behavior on Oracle?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-02 17:23:27 | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
| Previous Message | Tom Lane | 2009-08-02 16:29:19 | Re: IMMUTABLE break inlining simple SQL functions. |