Re: minor issue - one semicolumn too many in the docs - Mailing list pgsql-bugs

From Neil Conway
Subject Re: minor issue - one semicolumn too many in the docs
Date
Msg-id 1180797368.5297.0.camel@goldbach
Whole thread Raw
In response to minor issue - one semicolumn too many in the docs  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
List pgsql-bugs
On Sat, 2007-02-06 at 14:25 +0200, Frank van Vugt wrote:
> BEGIN;
>     SELECT * INTO STRICT myrec FROM emp WHERE empname = myname;
>     EXCEPTION
>         WHEN NO_DATA_FOUND THEN
>             RAISE EXCEPTION 'employee % not found', myname;
>         WHEN TOO_MANY_ROWS THEN
>             RAISE EXCEPTION 'employee % not unique', myname;
> END;
>
> The semicolumn after BEGIN was probably not meant to be there.

Thanks for the report. This was already fixed in CVS HEAD, but I
backported the fix to REL8_2_STABLE as well.

-Neil

pgsql-bugs by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: BUG #3331: Database Restoring problem
Next
From: "Laurent Hinault"
Date:
Subject: BUG #3341: Reinstallation error