Re: *** MUTEX access to data

[Pat Sherrill]

MySQL is a client/server product.  If you are writing a client, it is the
programmer's responsibility to handle the client threads (assuming you are
writing a multithreaded client) and notification of conflicts to the client
as well as select appropriate methods of locking.  I have not experienced
any deadlock situations with any current version of MySQL.

The most common issue generating the ODBC exception you describe below is a
table that does not have a Primary Key defined or is missing a TIMESTAMP(14)
column from the table.

I hope this helps.

Pat...

----- Original Message -----
From: Sébastien Ferrandez <sebastien@stripped>
To: MYSQL LIST <mysql@stripped>
Sent: Friday, November 19, 1999 3:38 AM
Subject: *** MUTEX access to data


> We have a problem with some guys here that are entering datat into our
> MySQL database. They complain about the impossibility to enter data at
> the same time, that they lose all changes but I guess MySQL is managing
> MUTEX access to data...Or should I put any instruction like (LOCK) when
> they modify data ?
> What solution do you think is best, and how do you explain this problem
> ? I'd express the MyODBC driver to send a dialog box saying "you cannot
> modify data because another user is currently in the process of doing
> it...). Really weird...
>
> --
> -------------------------------------------------------------------
>     Please Remove NO_SPAM before answering-Sébastien FERRANDEZ,
>     Junior Web developer at http://www.vinternet.fr.
>     fr.comp.infosystemes.www.auteurs.php, comp.databases.ms-access
>
>
>
>
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> posting. To request this thread, e-mail mysql-thread19110@stripped
>
> To unsubscribe, send a message to the address shown in the
> List-Unsubscribe header of this message. If you cannot see it,
> e-mail mysql-unsubscribe@stripped instead.
>
>