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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dong, Meng | 2001-08-01 10:18:15 | When dealing with 'bigint'or 'int8', the command 'copy'doesn't work |
Previous Message | pgsql-bugs | 2001-07-31 20:38:39 | ERROR: parser: parse error at or near "execute" |