| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Mike Aubury <mike(dot)aubury(at)aubit(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Michael Meskes <meskes(at)postgresql(dot)org> |
| Subject: | Re: keyword list/ecpg |
| Date: | 2008-06-13 14:39:48 |
| Message-ID: | 20080613143948.GN5534@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mike Aubury wrote:
> Theres also another thing that needs to be decided, which is if the generated
> ecpg grammer should be developer generated (ie. Michael Meskes runs a script
> and commits the output), or should be generated for each and every source
> based installation. I personally would stongly favour the script being a tool
> for ecpg tool developers and not used as part of a normal installation.
What happens when a non-Michael developer changes the original gram.y?
Is he expected to run the script before committing too? That sounds
brittle to me.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Aubury | 2008-06-13 14:53:03 | Re: keyword list/ecpg |
| Previous Message | Mike Aubury | 2008-06-13 13:57:54 | Re: keyword list/ecpg |