Re: plpgsql CASE statement - last version

Hello

2008/5/1 Jaime Casanova <systemguards(at)gmail(dot)com>:
> On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Hello
>>
>> I found some bugs when I used base_lexer, so I returned back own
>> lexer. It's only little bit longer, but simpler.
>>
>
> you really compile this one? i get a complain because
> read_sql_construct is called with 8 arguments and it should have only
> 7..

yes, I did it. 8 arguments are from EXECUTE USING patch
http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.108;r2=1.109;f=h

Pavel
.
>
> + expr = read_sql_construct(',', K_THEN, 0, "THEN",
> + "SELECT ", true, true, &tok);
>
>
> gram.y: In function 'plpgsql_yyparse':
> gram.y:1697: warning: passing argument 5 of 'read_sql_construct' makes
> integer from pointer without a cast
> gram.y:1697: warning: passing argument 7 of 'read_sql_construct' makes
> pointer from integer without a cast
> gram.y:1697: error: too many arguments to function 'read_sql_construct'
>
> --
> regards,
> Jaime Casanova
> Soporte de PostgreSQL
> Guayaquil - Ecuador
> Cel. (593) 087171157
>