On 08/29/2014 08:15 AM, geetanjali mehra wrote:
> But after doing *optimize table*, the value inside
> data_free is still the same. If there is no change in the value of
> data_free, then what *optimize table* does here?
Without seeing actual values I can only give an educated
guess:
* If you ar
Geetanjali,
There is a difference between next-key locking, gap locking and locking
reads.
Next-key locking and gap-locking are used with normal Selects statement in
Innodb, whereas locking reads wont release a lock on the whole column until
transaction completed, and not just selected values.
M
Could you please answer these questions also. What does data_free field
from SHOW TABLE STATUS shows?
When should we run optimize table for innodb tables?
I read various blogs. They said data_free shows free space inside the
innodb tables. But after doing *optimize table*, the value inside
data_f
Thanks for your reply.
I read those docs. Still my doubt is at the same stage. Please clarify the
same to me.
Should not other sessions be allowed to insert the rows beyond that
range.?
As far as I understand, Innodb brought the concept of next-key locks so as
to prevent phantom problem. So,
MicroOLAP Direct Access Components for MySQL and Delphi/C++ Builder (also
known as MySQLDAC) is a Borland Delphi/C++Builder component set for direct
connect to MySQL database server. DAC for MySQL allows you to create
Delphi/C++Builder applications without BDE, ODBC, ADO and without
libmysql.dll.
