Hi oyse,
Using autocommit or not is irrelevant in your present situation as it would not prevent the the lock row from being inserted in another transaction at the same time.
What you really nead is to LOCK your lock table:
mysql> LOCK TABLE locks WRITE;
mysql> SELECT * FROM locks where yourcond=true;
mysql> INSERT locks (...) VALUES(...);
mysql> UNLOCK TABLES;
Some notes:
- Don't forget to unlock the table, specially if your server is using persistent connections, like with Apache::DBI or pconnect in php, or no other connection will ever can lock the table.
- You can use LOCK TABLE locks READ if you just need to read the table, but you should use the WRITE lock for the select and the insert, or another thread can write after you read.
- Any connection that don't LOCK the table before attempting to do anything with it will success indepedently of the locks(, so you need to use the lock in every operation on this table).
- You should not do any operation that takes long (0.01+ secs) with LOCKS, as only one thread can LOCK the table at any time.
- All tables used after a lock and before an unlock must be locked.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|