| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PSQL commands: \quit_if, \quit_unless |
| Date: | 2016-12-02 17:24:05 |
| Message-ID: | CA+TgmoYztLgME9BepjBPMOL5q-z5gEVgeuYjhjVi4yyLN-acLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 2, 2016 at 11:12 AM, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> In order for me to understand how high the bar has been set, can you
> (Robert/Tom mostly, but I welcome any responses) explain what you mean by
> "full-blown expression language"? What constructs must it include, etc?
I mostly mean it should be based on flex and bison, not "this is so
simple I can just hand-roll it". I don't think it has much chance of
staying that simple.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-12-02 17:36:07 | pgsql: Introduce dynamic shared memory areas. |
| Previous Message | Tom Lane | 2016-12-02 16:52:32 | Re: PSQL commands: \quit_if, \quit_unless |