Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Function's final statement must be a SELECT
- From: "Dave Page" <dpage(at)pgadmin(dot)org>
- To: "Premil Agarwal" <preagarw(at)gmail(dot)com>
- Cc: pgsql-interfaces(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
- Subject: Re: Function's final statement must be a SELECT
- Date: Wed, 14 May 2008 21:49:24 +0100
- Message-id: <937d27e10805141349o40495dcdvc6292c1f98ed294(at)mail(dot)gmail(dot)com>
On Wed, May 14, 2008 at 9:38 PM, Premil Agarwal <preagarw(at)gmail(dot)com> wrote: > Tried that already, still the same error It (using plpgsql instead of sql) works fine for me using your code. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
- References:
- Function's final statement must be a SELECT
- From: Premil Agarwal
- Re: Function's final statement must be a SELECT
- From: Dave Page
- Re: Function's final statement must be a SELECT
- From: Premil Agarwal
- Function's final statement must be a SELECT
- Prev by Date: Re: [ADMIN] Function's final statement must be a SELECT
- Next by Date: pg_subtrans directory grows over 1 GB, is there a way to control it?
- Previous by thread: Re: Function's final statement must be a SELECT
- Next by thread: Re: [ADMIN] Function's final statement must be a SELECT
- Indexes: