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

2007-06-02 Thread Neil Conway
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 E

Re: [BUGS] BUG #3331: Database Restoring problem

2007-06-02 Thread Larry Rosenman
On Jun 2, 2007, at 10:32 AM, sajish wrote: The following bug has been logged online: Bug reference: 3331 Logged by: sajish Email address: [EMAIL PROTECTED] PostgreSQL version: 7.3 Operating system: Redhad Linux Description:Database Restoring problem Details: Get

[BUGS] BUG #3331: Database Restoring problem

2007-06-02 Thread sajish
The following bug has been logged online: Bug reference: 3331 Logged by: sajish Email address: [EMAIL PROTECTED] PostgreSQL version: 7.3 Operating system: Redhad Linux Description:Database Restoring problem Details: Get errors on Restore database via Pg_Restore or p

[BUGS] minor issue - one semicolumn too many in the docs

2007-06-02 Thread Frank van Vugt
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 EXCEPTI