| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "adjkldd(at)126(dot)com" <winterloo(at)126(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: confusing `case when` column name |
| Date: | 2024-03-12 14:37:56 |
| Message-ID: | A2904471-7798-45F5-8F21-F19907D365B2@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 12 Mar 2024, at 15:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> users are probably going to end up applying an AS clause most of
> the time if they care about the column name at all.
If anything, we could perhaps add a short note in the CASE documentation about
column naming, the way it's phrased now a new user could very easily assume it
would be "case".
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-03-12 14:40:19 | Re: Disable LLVM bitcode generation with pgxs.mk framework. |
| Previous Message | Robert Haas | 2024-03-12 14:27:48 | Re: On disable_cost |