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

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Shridhar Daithankar" <shridhar(at)frodo(dot)hserus(dot)net>, "Michael Meskes" <meskes(at)postgresql(dot)org>
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:15:27
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184CFF1@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2004-02-27 10:52:33 Re: Thread safe connection-name mapping in ECPG. Is it
Previous Message Karel Zak 2004-02-27 10:09:40 Re: [HACKERS] ORDER BY different locales