Hello,
KEY ACCOMPLISHMENTS LAST WEEK
=============================
Browse sql_show.cc and sql_base.cc source code, and know more the process of I_S.
KEY TASKS THAT STALLED LAST WEEK
==============================
do not yet extend the I_S wiki.
KEY GOOD VIBRATIONS
===================
More clear about the current implementation of I_S.
Like user performs "SELECT * FROM INFORMATION_SCHEMA", the process is:
get_all_tables -> open_normal_and_derived_tables -> open_tables ->
mysql_schema_table -> create_schema_table
->create_tmp_table ->get_new_handler (reach the storage engine level)
->schema_table_store_record -> ha_write_row
->issue storage engine write operation (almost heap).
The more detail is omitted here. Is there necessary to write the detail into I_S WIKI?
KEY CONCERNS
============
1. What does TALBLE_LIST store? May be used to pass I_S tables information? And What is
the relationship between TABLE_LIST and TABLE_SHARE?
2. What do devired tables mean?
3. Are all I_S tables created when user performs select statment about just one of tables
of I_S?
4. "SHOW TABLES" stament would issue I_S tables?
TASKS IN THE UPCOMING WEEK
==========================
1. Finish the skeleton of primary I_S storage engine. Do I need to post any code I write
to launchpad?
2. Continue to browse source code of current implementation of I_S.
Regards,
Robin.