Skip site navigation (1) Skip section navigation (2)

Re: plpgsql's case bug?

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:17:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Mar 28, 2010 at 12:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> It seems odd to require a dummy ELSE clause that does nothing just to
>> avoid having an exception thrown, but I'm not sure what else to make
>> of the quoted portion of the spec.  What do you think it's saying?
> I concur that we seem to be implementing the behavior the spec requires.

ok. it's seems it means what we have... remember english is not my
mother tongue ;)
and Oracle seems to be doing the same:

> As for the spelling of the error message, I don't believe that the spec
> intends to mandate any particular spelling of the text, only the value
> of the SQLSTATE code.  Were this not so, any translation of error
> messages would be a spec violation all by itself.

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...

Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2010-03-28 05:21:26
Subject: Re: plpgsql's case bug?
Previous:From: Tom LaneDate: 2010-03-28 05:15:32
Subject: Re: join removal

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group