Re: pgsql crollable cursor doesn't support one form ofpostgresql's cu

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: neilc(at)samurai(dot)com, bruce(at)momjian(dot)us
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql crollable cursor doesn't support one form ofpostgresql's cu
Date: 2007-04-27 05:36:33
Message-ID: BAY20-F2DA0AF96C31EA6FE22456F94F0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

it's true. There is bug. I'll send actualised version tomorrow.

Regards
Pavel

>I haven't read the rest of the thread yet, but is this hunk not buggy?
>yylex() is side-effecting, so the two calls to yylex() do not do what
>the comment suggests.
>
> >
> > ! /* check FROM or IN keyword after direction's specification */
> > ! if (check_FROM && (yylex() != K_FROM && yylex() != K_IN))
> > ! yyerror("expected \"FROM/IN\"");
> >
> > return fetch;
>
>-Neil
>
>

_________________________________________________________________
Emotikony a pozadi programu MSN Messenger ozivi vasi konverzaci.
http://messenger.msn.cz/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zoltan Boszormenyi 2007-04-27 06:08:14 Re: New version of GENERATED/IDENTITY, was Re: parser dilemma
Previous Message Neil Conway 2007-04-27 05:01:14 Re: pgsql crollable cursor doesn't support one form of postgresql's cu