The i_s was introduced against my intention. (So, I didn't document about the i_s)
I think this should be removed from XtraDB, even it is very useful for debugging / developing,
if it blame about internal information cheaply.
The internal information may change for each versions and I cannot explain the meanings for not-well-known users.
And I cannot keep exact explanation about it in the future.
I suggest .....
1. remove the i_s
or
2. document "don't use if you don't read source code because it is raw dump of the internal table. it is for InnoDB, not for users"
* I can imagine the users next complain... the N_COL is wrong when don't use PK.
I should say again "don't use it, if you don't know innodb internal".... It may present the internal columns...
I think newer InnoDB-Plugin has similar table. Please wait official i_s.
I am tired about blaming about not to understand internal information.
The i_s was introduced against my intention. (So, I didn't document about the i_s)
I think this should be removed from XtraDB, even it is very useful for debugging / developing,
if it blame about internal information cheaply.
The internal information may change for each versions and I cannot explain the meanings for not-well-known users.
And I cannot keep exact explanation about it in the future.
I suggest .....
1. remove the i_s
or
2. document "don't use if you don't read source code because it is raw dump of the internal table. it is for InnoDB, not for users"
* I can imagine the users next complain... the N_COL is wrong when don't use PK.
I should say again "don't use it, if you don't know innodb internal".... It may present the internal columns...
I think newer InnoDB-Plugin has similar table. Please wait official i_s.
I am tired about blaming about not to understand internal information.