I could fix this if I changed the table type to InnoDB, correct?
Quoting Jeremy Zawodny <Jeremy@stripped>:
> On Mon, Aug 18, 2003 at 10:41:55AM -0700, jkelty@stripped wrote:
> > Hello,
> > I just have a question about the table locking in 3.23.56. If I am
> inserting a
> > row into a table that is MyISAM type, is the entire table locked?
> > And, if so, what does this mean for concurrent selects?
> An INSERT obtains a WRITE lock on the table, so no concurrent reads
> can happen until the write lock is released and someone obtains a READ
> There's a special case: a MyISAM table with fixed-length rows and no
> deleted records allows for INSERTs to happen with SELECTs running.
> Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
> <Jeremy@stripped> | http://jeremy.zawodny.com/
> MySQL 4.0.13: up 17 days, processed 869,429,243 queries (591/sec. avg)