* Slava Akhmechet <coffeemug@stripped> [09/07/02 04:19]:
> I would like to place code into the store_lock method of our custom
> storage engine to turn off all locking (we manage our own locks, and
> don't want MySQL to lock anything on our behalf). At the moment I have
> code that looks like this:
> THR_LOCK_DATA **ha_edb::store_lock(THD *thd,
> THR_LOCK_DATA **to,
> enum thr_lock_type lock_type)
> return to;
> Is this correct? I'm not sure if this is the code I need to downgrade
> all locks to "no locking".
Can your engine process DROP TABLE concurrently with SELECT?
Do you really want MySQL statements LOCK TABLE <table> WRITE and
FLUSH TABLE have no effect on your engine, i.e. allow them to
proceed concurrently with all statements and each other?