Hi there,
On Wed, 17 Jan 2001, Sinisa Milivojevic wrote:
>
> First of all, you should not over-complicated things. Even in our
> server we do not call fork, as we have threads.
I don't want to call fork, because there are advantages of using threads
in this process (not involving mysql) that I
Kyle Cronan writes:
> Sinisa,
>
> My process has three threads and three different MYSQL structures.
> I have found that if I don't let the three mysql_real_connect() calls go
> one by one when I spawn the daemon, and then wait in each thread for them
> all to finish, I get an error that
Sinisa,
On Mon, 15 Jan 2001, Sinisa Milivojevic wrote:
> Hi!
>
>
> I will answer questions one by one.
>
>
> 1) thread safe client library only has mutexes around thread sensitive
> code. They have nothing to do with timeouts. Timeouts can be resolved
> with corresponding startup variables
Kyle Cronan writes:
> I have read through the archives and am still unclear on a few things:
>
> o Does libmysqlclient_r only correct the timeout problem? Or does it
>provide thread safe versions of calls like mysql_query()? I do not
>need to use timeouts.
>
> o I will definat
e any help.
Thank you,
Kyle Cronan
<[EMAIL PROTECTED]>
-- Forwarded message --
Date: Fri, 5 Jan 2001 11:55:44 + (/etc/localtime)
From: Kyle Cronan <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Thread safe client with C api (repost)
Further work has led me to believe
