Re: InnoDB to MyISAM

[Jeremiah Gowdy]

> Hi,
> If you're loocking for consurrent inserts/deletes, use innodb (row level
> locking). This will be better than myisam.

I'm looking for concurrent inserts / selects, reading and writing.  The key 
is to get the reads and blocking writes (writes that need the insert ID, 
which can't be done DELAYED) done as quickly as possible.  Deletes are 
relatively unimportant as long as the primary record is marked deleted. 
Cleaning up the FK linked records is of no consequence in this particular 
application, and can be deferred to a nightly process.

> This will ceratinly be faster since insert or delete on myisam implies a 
> LOCK
> table implicit mecanism.

Insert does not imply a LOCK TABLE if there are no deleted records.