| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Mike Aubury <mike(dot)aubury(at)aubit(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Meskes <meskes(at)postgresql(dot)org> |
| Subject: | Re: keyword list/ecpg |
| Date: | 2008-06-13 09:47:55 |
| Message-ID: | 20080613094755.GA25819@feivel.credativ.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[Sorry, just noticed that I didn't answer this email. ]
On Wed, Jun 04, 2008 at 05:06:41PM +0100, Mike Aubury wrote:
> It might depend on the tokens..
> Are ">=", "++" etc single tokens ?
> ...
> > Wouldn't it work to just always insert a space between tokens, no matter
> > whether there was one originally?
There are a few cases where you must not enter a blank, but I'm not sure
whethere these are all in ecpg specific rules anyway. One example that
comes to my mind is the handling of ":<port>" in the connect statement.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Aubury | 2008-06-13 09:55:51 | Re: keyword list/ecpg |
| Previous Message | Zdenek Kotala | 2008-06-13 09:26:07 | Re: Proposal: Multiversion page api (inplace upgrade) |