Never mind. This was simply my mistake. mysqld had a different copy of
the table in it's cache, so the problem went away when I restarted the
server process.
Thanks anyway,
Kyle Cronan
<[EMAIL PROTECTED]>
-
Bef
o is that the above warning
seems invalid; SHOW processlist reports no client threads accessing this
table.
Even so, why would this cause the problem running the DELETE query? And
attempting to repair the table with myisamchk gets rid of the above
warning but doesn't fix the problem with the quer
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
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
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
