Hi Stewart,
On 18/12/2008, at 9:29 AM, Stewart Smith wrote:
On Wed, Dec 17, 2008 at 11:36:01AM -0500, Sheeri K. Cabral wrote:
While I agree with this, one of the benefits of auto-discovery
(with rules
such as databases) is that databases and tables that do not rely on
centralized information (such as MyISAM) can be easily transferred to
another machine. Lots of people using innodb_file_per_table want
the easy
ability to copy a single table or a few tables to another file,
like they
can with MyISAM tables.
I'm not sure that both can be done, unless there could be an easy
way to
export data dictionary/metadata information on a table basis (ie,
in an
innodb model, copy a few tables' .frm and .ibd files, and export an
ibdata
file with the centralized info for just those tables).
To be honest, I'm not sure how file-per-table and IMPORT TABLESPACE
work..
*if* the data dictionary part is in the ibd, i think it'd be
trivial.... but I'm not sure it is.
Unfortunately, it's not. The InnoDB data dictionary is in the global
tablespace.
Percona has been looking at shifting it into the IBD file for file-per-
table, but apparently it's not trivial.
Cheers,
Arjen.
--
Arjen Lentz, Director @ Open Query (http://openquery.com.au)
MySQL Training from $475/day, DBA/Support from $249/month
My blog is at http://arjen-lentz.livejournal.com
OurDelta: free enhanced builds for MySQL @ http://ourdelta.org
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
