Re: Blocking Selects with LOCK TABLES

2004-05-10 Thread Lou Olsten
<< Looks like it's a query cache issue. In this case you get result from the cache.>> That was it. THANKS - Original Message - From: "Victoria Reznichenko" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 10, 2004 1:20 PM Subject

Re: Blocking Selects with LOCK TABLES

2004-05-10 Thread Robert A. Rosenberg
At 12:40 -0400 on 05/10/2004, Lou Olsten wrote about Blocking Selects with LOCK TABLES: According to the docs (http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html) : If a thread obtains a READ lock on a table, that thread (and all other threads) can only read from the table. If a thread obtains

Re: Blocking Selects with LOCK TABLES

2004-05-10 Thread Victoria Reznichenko
"Lou Olsten" <[EMAIL PROTECTED]> wrote: > According to the docs (http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html) > : > If a thread obtains a READ lock on a table, that thread (and all other threads) can > only > read from the table. If a thread obtains a WRITE lock on a table, only the thread

Blocking Selects with LOCK TABLES

2004-05-10 Thread Lou Olsten
According to the docs (http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html) : If a thread obtains a READ lock on a table, that thread (and all other threads) can only read from the table. If a thread obtains a WRITE lock on a table, only the thread holding the lock can read from or write to the ta