Re: [HACKERS] parser problem

Thomas G. Lockhart writes:
> where <condition> is one of:
>
>   sqlwarning
>   sqlerror
>   sqlmessage
>   not found
>   dbevent

At the moment we only can sqlerror and not found.

>   continue
>   stop
>   goto <label>

Got these plus go to <label> and sqlprint.

>   call <procedure>

Hmm, this is called "do" in Oracle. I think I allow both for compatibility.

> where <procedure> cannot be called with any arguments. This syntax would
> be easy to parse with your existing lexer. My SQL books shows an even
> more limited syntax with only "continue" and "goto" allowed.

Yes, but we don't have to play it down to the standard, do we? :-)

> If you want to allow some other syntax, including double-quoted strings,
> then you will need to implement it explicitly in your grammar.

IMO an argument is a very good idea. So I have to think about it a little
bit more.

Michael
--
Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
meskes@debian.org                      | 52146 Wuerselen
Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10