Re: Thread safe connection-name mapping in ECPG. Is it - Mailing list pgsql-hackers

From Shridhar Daithankar
Subject Re: Thread safe connection-name mapping in ECPG. Is it
Date
Msg-id 403F2171.1080408@frodo.hserus.net
Whole thread Raw
In response to Re: Thread safe connection-name mapping in ECPG. Is it  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
Responses Re: Thread safe connection-name mapping in ECPG. Is it  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Zeugswetter Andreas SB SD wrote:

>>I am asking for CONNECTION being a variable of data type 'connection *' rather 
>>than 'const char *'. That would avoid name lookups.
>>
>>Is that out of spec?
> Yes, but the preprocessor could still add an optimization ala 'connection *' for
> the hardcoded cases (exec sql set connection 'myconn1'; exec sql at 'myconn1' ...).
> It needs to maintain the string list for the non hardcoded cases though.

How about, allowing 'connection *'? If somebody puts a 'connection *' there it 
is used. If it is a string a name search is performed. Best of both worlds.

Can that be an acceptable compromise?
 Shridhar


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: Thread safe connection-name mapping in ECPG. Is it
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: Tablespaces