Content-Type: text/plain;
  charset="iso-8859-1"
From: Philip Yarra <philip@utiba.com>
Organization: Utiba
To: Michael Meskes <meskes@postgresql.org>
Subject: Re: ECPG thread-safety
Date: Mon, 31 Mar 2003 11:23:04 +1100
User-Agent: KMail/1.4.1
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	pgsql-interfaces@postgresql.org
References: <200303280200.h2S20N218363@candle.pha.pa.us>
	<200303281749.04746.philip@utiba.com>
	<20030330140605.GB8326@feivel.fam-meskes.de>
In-Reply-To: <20030330140605.GB8326@feivel.fam-meskes.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200303311023.04279.philip@utiba.com>

On Mon, 31 Mar 2003 00:06, Michael Meskes wrote:
> Is this the only problem you're facing with Informix? I'm currently
> working on other Informix compatibility stuff. And I'd like to get that
> tested as good as possible.

Yes, I recall reading that you were working on better Informix compatibilit=
y -=20
most welcome! Honestly, the changes we needed to make to port from Informix=
=20
were pretty minor, as I recall:=20
- some of the connection syntax differred
- figuring out that OID was not populated in sqlca if not auto-committing=
=20
(makes sense really)
- our original code used non-standard ways to name a PREPAREd statement whi=
ch=20
threw ECPG (and according the Informix doco shouldn't really have worked fo=
r=20
that either!) so I fixed that in both development streams

You can probably deduce from this that we are not really using a great deal=
 of=20
functionality in this app - what we have ported so far is a simple logging=
=20
server. We really won't be porting any more until ECPG is thread-safe. It's=
 a=20
major show-stopper, since all of our apps are built on the same (pthreads)=
=20
framework.

That said, we would love to help test further Informix compatibility stuff =
-=20
anything that makes our future porting process easier would be welcome! Let=
=20
us know what you'd like us to test. Diffs are fine.

Regards, Philip.