| From: | "Richard Huxton" <dev(at)archonet(dot)com> | 
|---|---|
| To: | "Jan Wieck" <JanWieck(at)yahoo(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: plpgsql: RAISE <level> <expr> <params> | 
| Date: | 2001-07-23 16:14:38 | 
| Message-ID: | 006601c11392$95935be0$1001a8c0@archonet.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
From: "Jan Wieck" <JanWieck(at)yahoo(dot)com>
> Tom Lane wrote:
> > and then the code takes care of swallowing expressions until ';',
> > similarly to the way SQL commands are handled.  (plpgsql's parsing
> > methodology is sinfully ugly, isn't it?  But I don't suppose you
> > want to try to replace it...)
>
>     It  is,  indeed,  and I'm sorry for that. But it was the only
>     way I saw to make new features in the PostgreSQL  main  query
>     engine  automatically  available in PL/pgSQL without a single
>     change.
Actually, I like the idea of using the SQL system to evaluate expressions -
why reinvent the wheel?
The only thing needed for this is a grammar for expressions so we can mix
and match with RAISE a bit better. First draft doesn't look too bad - I can
not deal with function-calls and brackets and still have something useful.
- Richard Huxton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Howe | 2001-07-23 17:25:47 | Re: Large queries - again... | 
| Previous Message | Hsin Lee | 2001-07-23 15:03:29 | Question about porting the PostgreSQL |