| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql's case bug? |
| Date: | 2010-03-28 05:21:26 |
| Message-ID: | 13355.1269753686@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
> well actually i get here when translating the plpgsql messages and
> found very strange a message like "case not found", and as a last
> argument (a weak one, i have to admit) i will say that the hint could
> be innecesary if we use the same message the spec is suggesting... but
> i won't die for this, so...
I don't think so ... the spec's wording doesn't seem to me to suggest at
all that you should insert an ELSE clause. It just looks redundant :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-03-28 05:42:03 | Re: plpgsql's case bug? |
| Previous Message | Jaime Casanova | 2010-03-28 05:17:27 | Re: plpgsql's case bug? |