scheduling, priorities etc

[another oracle dba]

Hi all:

I have read somewhere that mysql allows inserts into a table
without "holes" to go concurrently with the reads from that table.
starting at v 3.23.7. I'm running 3.23.41-nt and have tried to 
accomplish that, but couldn't. My reads seem to only start after
the inserts are completed. Is there a special parameter I need to
set up to enable this feature? I'm also having the same problem
with low_priority/high_priority features. I have done some testing
and couldn't force an update to run after the select no matter what.
Any ideas what I may be doing wrong?

thanks

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com