| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Failure to coerce unknown type to specific type |
| Date: | 2015-05-03 19:20:38 |
| Message-ID: | 691275181.611927.1430680838706.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> The spec section 6.11 1) c) very explicitly requires
> COALESCE(NULL, NULL)
> be the exact equivalent of
> CASE WHEN NULL IS NOT NULL THEN NULL ELSE NULL END
>
> Yet in PostgreSQL the long form of the CASE clause returns the
> same thing as a bare NULL, while the short form (COALESCE) gives
> an error.
Never mind; I got confused in my testing -- they both return NULL
of type text. I'll dig on that one some more.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-03 19:28:03 | Re: Failure to coerce unknown type to specific type |
| Previous Message | Kevin Grittner | 2015-05-03 18:56:14 | Re: Failure to coerce unknown type to specific type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-03 19:28:03 | Re: Failure to coerce unknown type to specific type |
| Previous Message | Pavel Stehule | 2015-05-03 19:18:24 | Re: Manipulating complex types as non-contiguous structures in-memory |