Re: Possible bug in ECPGlib thread-safety (Postgres - Mailing list pgsql-interfaces

From Philip Yarra
Subject Re: Possible bug in ECPGlib thread-safety (Postgres
Date
Msg-id 200312161223.30595.philip@utiba.com
Whole thread Raw
In response to Re: Possible bug in ECPGlib thread-safety (Postgres  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Possible bug in ECPGlib thread-safety (Postgres
Re: Possible bug in ECPGlib thread-safety (Postgres
List pgsql-interfaces
On Tue, 16 Dec 2003 12:08 pm, Bruce Momjian wrote:
> I have updated the 7.4.X does and CVS head docs to mention that ecpg SET
> CONNECTION is not thread-aware, and I have added this to the ecpg TODO:
>
>         o Make SET CONNECTION thread-aware

One thing that concerns me: I doubt this is supported in other database
systems... people who relied on this feature in ECPG would likely encounter
threading bugs if they port their code to other DBs. And threading bugs can
be nasty to find. Does anyone know how other DBs handle this issue?

I thinks it's a worthy feature, but perhaps the pre-compiler should warn
people that they are relying on non-standard behaviour?

Philip.


pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Next
From: Bruce Momjian
Date:
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres