-
Thirunarayanan Balathandayuthapani authored
Problem: ======== With current InnoDB tablespace implementation with newDD, the implicit (file-per-table) tablespace name is named as "innodb_file_per_table_x", where x is the tablespace ID. The disadvantage of this is that the tablespace name is hard for user to find out. This makes it a bit harder for user to specify tablespace name for import/export tablespace etc. Solution: ======== In case of file_per_table tablespace, rename tablespace name from innodb_file_per_table_<space_id> to tablespace name in mysql.tablespaces table. Reviewed-by:
Jimmy Yang <jimmy.yang@oracle.com> Reviewed-by:
Bin Su <bin.x.su@oracle.com> Reviewed-by:
Dyre Tjeldvoll <dyre.tjeldvoll@oracle.com> RB: 16669
Thirunarayanan Balathandayuthapani authoredProblem: ======== With current InnoDB tablespace implementation with newDD, the implicit (file-per-table) tablespace name is named as "innodb_file_per_table_x", where x is the tablespace ID. The disadvantage of this is that the tablespace name is hard for user to find out. This makes it a bit harder for user to specify tablespace name for import/export tablespace etc. Solution: ======== In case of file_per_table tablespace, rename tablespace name from innodb_file_per_table_<space_id> to tablespace name in mysql.tablespaces table. Reviewed-by:
Jimmy Yang <jimmy.yang@oracle.com> Reviewed-by:
Bin Su <bin.x.su@oracle.com> Reviewed-by:
Dyre Tjeldvoll <dyre.tjeldvoll@oracle.com> RB: 16669
Loading