From: | Michael Meskes <meskes(at)topsystem(dot)de> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker) |
Subject: | Re: [HACKERS] parser problem |
Date: | 1998-04-23 07:31:43 |
Message-ID: | 199804230731.JAA30091@gauss.topsystem.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1998-04-23 07:33:45 | Just another question |
Previous Message | t-ishii | 1998-04-23 04:05:41 | Re: [HACKERS] multi-byte aware char_length() etc. |