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

From: Neil Conway <neilc(at)samurai(dot)com>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: minor issue - one semicolumn too many in the docs
Date: 2007-06-02 15:16:08
Message-ID: 1180797368.5297.0.camel@goldbach
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dorofeev A.V. 2007-06-03 13:12:33 BUG #3339: postgis astext() function returns broken string through ODBC
Previous Message Larry Rosenman 2007-06-02 13:38:14 Re: BUG #3331: Database Restoring problem