| From: | Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Thread safe connection-name mapping in ECPG. Is it |
| Date: | 2004-02-27 10:52:33 |
| Message-ID: | 403F2171.1080408@frodo.hserus.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB SD | 2004-02-27 11:39:06 | Re: Tablespaces |
| Previous Message | Zeugswetter Andreas SB SD | 2004-02-27 10:15:27 | Re: Thread safe connection-name mapping in ECPG. Is it |