Skip site navigation (1) Skip section navigation (2)

Re: ERROR: parser: parse error at or near "execute"

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: chris_br(at)email(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: ERROR: parser: parse error at or near "execute"
Date: 2001-07-31 22:43:14
Message-ID: Pine.BSF.4.21.0107311542030.2920-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Tue, 31 Jul 2001 pgsql-bugs(at)postgresql(dot)org wrote:

> Christian Villa Real Lopes (chris_br(at)email(dot)com) reports a bug with a severity of 3
> The lower the number the more severe it is.
> 
> Short Description
> ERROR:  parser: parse error at or near "execute"
> 
> Long Description I created a function to drop a table if it exists. On
> pgsql-7.0.3 this function returns an error, as follow :
> 
> template1=# SELECT func_drop_table('friend');
> ERROR:  parser: parse error at or near "execute"
> 
> On pgsql-7.1.2 this function works fine and no error returns just the following lines :

IIRC, execute was added in 7.1.


In response to

pgsql-bugs by date

Next:From: Dong, MengDate: 2001-08-01 10:18:15
Subject: When dealing with 'bigint'or 'int8', the command 'copy'doesn't work
Previous:From: pgsql-bugsDate: 2001-07-31 20:38:39
Subject: ERROR: parser: parse error at or near "execute"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group