Suggestion:
Because the Ecpg project uses a global sqlca, it can be accessed by only
one thread at a time.
If (instead) we had a user supplied sqlca, it could be used by multiple
threads.
Why not have the user allocate the sqlca or pass it in as a parameter
(maybe they want an auto sqlca).
In any case: a single, global sqlca is a very bad thing. (IMO-YMMV).

Question:
Why no sqlda structure?  Every other embedded SQL I have used has the
sqlda {and it is darn useful}.

Mon, 4 Feb 2002 16:51:38 -0800
"Dann Corbit" <DCorbit@connx.com>
Ecpg and reentrancy
On Mon, Feb 04, 2002 at 04:51:38PM -0800, Dann Corbit wrote:
> Because the Ecpg project uses a global sqlca, it can be accessed by only
> one thread at a time.

That's correct.

> If (instead) we had a user supplied sqlca, it could be used by multiple
> threads.

How do you want to supply it? 

> Why not have the user allocate the sqlca or pass it in as a parameter
> (maybe they want an auto sqlca).

That's not exactly the way other RDBMS handle it. Thus compatibility might
become a problem. 

> In any case: a single, global sqlca is a very bad thing. (IMO-YMMV).

Okay, let's talk about a better way.

> Question:
> Why no sqlda structure?  Every other embedded SQL I have used has the
> sqlda {and it is darn useful}.

Noone volunteered to implement it. :-)

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

Tue, 5 Feb 2002 15:33:04 +0100
Michael Meskes <meskes@postgresql.org>
Re: Ecpg and reentrancy