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

From Frank van Vugt
Subject minor issue - one semicolumn too many in the docs
Date
Msg-id 200706021425.47923.ftm.van.vugt@foxi.nl
Whole thread Raw
Responses Re: minor issue - one semicolumn too many in the docs  (Neil Conway <neilc@samurai.com>)
List pgsql-bugs
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.

pgsql-bugs by date:

Previous
From: "Thekkayil Joy Thomas"
Date:
Subject: BUG #3329: Issue with INSERT INTO for japanese katakana characters.
Next
From: "sajish"
Date:
Subject: BUG #3331: Database Restoring problem