Re: Thread safe connection-name mapping in ECPG. Is it
| От | Shridhar Daithankar |
|---|---|
| Тема | Re: Thread safe connection-name mapping in ECPG. Is it |
| Дата | |
| Msg-id | 403F2171.1080408@frodo.hserus.net обсуждение исходный текст |
| Ответ на | Re: Thread safe connection-name mapping in ECPG. Is it ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>) |
| Ответы |
Re: Thread safe connection-name mapping in ECPG. Is it
|
| Список | 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 по дате отправления: