| From: | Christof Petig <christof(at)petig-baender(dot)de> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ecpg - GRANT bug |
| Date: | 2001-10-19 07:37:59 |
| Message-ID: | 3BCFD856.E2E1F28C@petig-baender.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Meskes wrote:
> On Tue, Oct 16, 2001 at 10:27:42AM +0100, Lee Kindness wrote:
> > And the patch below corrects a pet peeve I have with ecpg, all errors
> > and warnings are output with a line number one less than reality...
>
> I wish I knew where this comes from. I've been trying to track this bug down
> for years now, but have yet to find the reason. Okay, didn't check for quite
> some time now, but the first time I committed a fix was March 1998. But
> somehow I still haven't found all problems it seems.
I somewhat got the impression that using C++ style comments (//) are related
to worse the problem. But I must confess I didn't dig deep enough to contribute
anything substancial. Perhaps the problem is a misunderstanding of ecpg and
cpp.
I was confused by the blank lines following or preceding a #line statement
every time I looked at it. This should be not necessary.
While talking about warnings: ecpg warns about NULLIF being not implemented
yet. But actually it works (for me).
Christof
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2001-10-19 14:36:49 | Re: ecpg - GRANT bug |
| Previous Message | Hiroshi Inoue | 2001-10-19 02:36:16 | Re: Bug #487: Erroneus values of BOOLEANS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Hallam | 2001-10-19 08:02:01 | Re: ODBC SQLBindParameter and UNICODE strings |
| Previous Message | Thomas Lockhart | 2001-10-19 06:19:43 | Does "postmaster -i"... |