On 03/04/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> >> What exactly are you trying to accomplish?
>
> > when I build CASE expression, I have to merge some PLpgSQL_expr
> > together. Then I have to reparse expr->query and I have to find params
> > a
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> What exactly are you trying to accomplish?
> when I build CASE expression, I have to merge some PLpgSQL_expr
> together. Then I have to reparse expr->query and I have to find params
> and actualize it.
There has to be a better way than that. What CA
>
>
> No, you don't. Whatever you think you need those for, there's probably
> a better way to do it. We got out of the business of letting anything
> but scan.c and gram.c depend on Bison symbol numbers years ago, and
> I don't much want to re-introduce that dependency.
>
> What exactly are
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> I would to use main scanner from plpgsql. I need some values from
> parser/parse.h
> #define SELECT 543
> #define PARAM 642
No, you don't. Whatever you think you need those for, there's probably
a better way to do it. We got out of the business of
Hello
I would to use main scanner from plpgsql. I need some values from parser/parse.h
#define SELECT 543
#define PARAM 642
and YYSTYPE
any ideas how to do it?
I would not copy it by hand.
Regards
Pavel Stehule
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
