Re: How do I know which transaction lock a table?

[john walker]

> The transaction has nothing to do with the MyISAM
> table. Any SQL on a MyISAM table locks the
> table.
sorry abount that, one of my friend tell me that, and i didn't confirm it.
> ALTER (before 5.6) locks the table, whether or not
> you see "Locked".
I know that, but the situation is the alter statement was "Waiting for table metadata lock alter table" as i see from "show procecclist" and my alter statment was the only statment operating the table.
> That is a kludge (if the table was already
> MyISAM). Why are you doing it?
I'm confirm whether all the alter statement all locked. and i can't drop any columns from the table.
> That is a worse kludge; why are you doing it? If
> you need control over an AUTO_INCREMENT value,
> perhaps you don't need AUTO_INCREMENT? Or you can
> explicitly provide the value?
The same as above.
> For "online payments" you _really_ should be using
> InnoDB and carefully crafted transactions. They
> might understand this when you have a crash and
> the money fails to add up right.
This is not the thing i can decide, i will persuade them to do it. and redesign the data design