FreeTDS Development Group

["James K. Lowden" <jklowden AT schemamania.org>]

On Tue, 16 Dec 2003, "ZIGLIO Frediano" <Frediano.Ziglio AT vodafone.com>
wrote:
> I think it's a big problem. 

Me too.  It affects developers the most, but it hinders users, too. 

> The simplest way to remove this
> problem is to use only a global dump (not for every connection). This
> mean to remove dumpfile fields from tds_connect_info/login_info and
> accept it only on global section. Another problem is related to thread.
> We write process id in log so to detect differents process (as in
> apache) however on multithreaded environments where getpid() on thread 1
> == getpid() on thread 2 (ie apache2 using thread and linux with native
> posix thread support) it's impossible to detect which thread did the
> operation.

Rather than process/thread ID, I think spid would be the best identifier
to use.  I don't think even multithreaded applications share sessions.  

> perhaps it's better to leave per-connection iconv as it is... 

You're probabably right.  It's even possible for a client to change his
charset, and to support multiple client charsets simultaneously.  

--jkl