
> I'm not sure I understand you correctly. The SQL standard says you can
> call your statement as this:
> exec sql at CONNECTION select 1;
> 
> Here CONNECTION of course is a string, the name of the connection. So,
> yes, we have to maintain that list to make sure we get the right
> connection.

I thought the main problem was an "exec sql set connection :hostvar",
where hostvar is a string determined at runtime. Else above could be translated at 
precompile time to anything more efficient than a string search.

Oh, just noticed above is not standard, but sure is very useful.

Andreas

Fri, 27 Feb 2004 10:14:12 +0100
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: Thread safe connection-name mapping in ECPG. Is it required?