Skip site navigation (1) Skip section navigation (2)

Re: Thread safe connection-name mapping in ECPG. Is it required?

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Michael Meskes" <meskes(at)postgresql(dot)org>,"Shridhar Daithankar" <shridhar(at)frodo(dot)hserus(dot)net>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Thread safe connection-name mapping in ECPG. Is it required?
Date: 2004-02-27 09:14:12
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184CFEF@m0114.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

pgsql-hackers by date

Next:From: Shridhar DaithankarDate: 2004-02-27 09:32:22
Subject: Re: Thread safe connection-name mapping in ECPG. Is it
Previous:From: Zeugswetter Andreas SB SDDate: 2004-02-27 09:00:29
Subject: Re: Tablespaces

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group