Re: why does documentation use "END CASE" when that doesn't work - Mailing list pgsql-general

From Tom Lane
Subject Re: why does documentation use "END CASE" when that doesn't work
Date
Msg-id 4511.1393375427@sss.pgh.pa.us
Whole thread Raw
In response to why does documentation use "END CASE" when that doesn't work  (Susan Cassidy <susan.cassidy@decisionsciencescorp.com>)
List pgsql-general
Susan Cassidy <susan.cassidy@decisionsciencescorp.com> writes:
> The documentation says:
> CASE search-expression
>     WHEN expression [, expression [ ... ]] THEN
>       statements
>   [ WHEN expression [, expression [ ... ]] THEN
>       statements
>     ... ]
>   [ ELSE
>       statements ]
> END CASE;

> And it repeats the "END CASE" phrase in other examples.

> However, that doesn't work.  You have to just use "END".

> Shouldn't the documentation be fixed?

No ... you're confusing the SQL CASE expression with the plpgsql CASE
statement.

http://www.postgresql.org/docs/9.3/static/functions-conditional.html

http://www.postgresql.org/docs/9.3/static/plpgsql-control-structures.html#PLPGSQL-CONDITIONALS

It's a bit unfortunate that plpgsql's statement looks enough like the
expression to cause confusion, yet not exactly like the expression.
The decorated END is consistent with other things in plpgsql such as
END IF, though.

            regards, tom lane


pgsql-general by date:

Previous
From: Susan Cassidy
Date:
Subject: why does documentation use "END CASE" when that doesn't work
Next
From: Jov
Date:
Subject: Re: why does documentation use "END CASE" when that doesn't work