Re: ecpg Oracle compatibility issue

From: Roland Karch <rdkarch(at)immd3(dot)informatik(dot)uni-erlangen(dot)de>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ecpg Oracle compatibility issue
Date: 2002-12-13 19:28:05
Message-ID: 20021213192805.GA28737@faui31x.informatik.uni-erlangen.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Dec 12, 2002 at 04:49:30PM -0500, Bruce Momjian wrote:
> I applied the attached patch. Your version looked like it would have
> doubled the double-quotes.

Oops - yes, I got that wrong.

> As you mentioned, you couldn't get bison to
> work, so you weren't able to test it. Please look over this patch and
> make sure it is correct.

It works fine, just got bison to work on my other computer.

> Also check the other use of ECPGdisconnect().
> Is that correct? Does it need "CURRENT"?

Yes, it's needed. Supplying a NULL pointer instead results in a segfault
for me. However, it would work if src/interfaces/ecpg/lib/connect.c line
468 was patched - checking for NULL before dereferencing a user-supplied
pointer is generally a good idea.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2002-12-13 20:29:08 Re: ecpg Oracle compatibility issue
Previous Message Tom Lane 2002-12-13 18:12:05 Re: server terminated by a query in 7.3