Hi!
>>>>> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Uwe Heldt writes:
>> Hi Venu,
>>
>> it ' s hard to send you sample code. The database access is coded over more
>> then one class which dynamicly build sql statements. The only thing i know
>> is, that first a simple select is performed. After that one update on the
>> same table row and then a select again. Could id be that there is a lock on
>> this row if the statements appear to quickly? What does means "Communication
>> Link failure" in this context?
<cut>
Sinisa> to fix a bug, if there is any.
Sinisa> "Communication ..." error may come up if there was an incongruency in
Sinisa> code sequence. This can happen if all rows from result set have not
Sinisa> been fetched and you have issued another query.
Sinisa> In that case that is an error in application code.
It could also be that the server did a timeout on the connection
(which may happen if 'write_timeout' is low and you didn't fetch the
rows fast enough in your client).
A last option is if the mysqld server died during the query.
By examing the 'hostname'.err file in the mysqld data directory, you
should get an idea which of the above cases that is causing you a
problem.
Regards,
Monty
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
