Thread: minor issue - one semicolumn too many in the docs

minor issue - one semicolumn too many in the docs

From
Frank van Vugt
Date:
Hi,

I noticed that the example code for SELECT STRICT mentioned in the docs
(v8.2.4) under "37.6.3. Executing a Query with a Single-Row Result" mentions:

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.


--
Best,




Frank.

Re: minor issue - one semicolumn too many in the docs

From
Neil Conway
Date:
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