to make the user interface simple, I decided to take the table per file
approach. Each .ibd file is internally a 'tablespace'.
The simple approach I chose is similar to how MyISAM now works. I thought it
would be nice for current MySQL users.
In Oracle, one can store several tables into a single named tablespace, and
can also split indexes and data of a single table to separate tablespaces.
Nothing prevents adding those features to InnoDB, too. It just requires new
syntax in CREATE TABLE to specify these options.
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM
From: "Eduardo D Piovesam" (eduardo@stripped)
Subject: Re: MySQL/InnoDB-4.0.16 is released + sneak peek of 4.1.1
View this article only
Date: 2003-10-23 14:43:28 PST
(Sorry for the last email, it's not complete).
Sorry, but I didn't understand the concept of tablespace applied. It's
different from Oracle, right?
AFAIK, tablespace is utilized to logically group "tables" into one (or more)
And to group "indexes" into another files...
But you said that the each table (with its indexes) will be in one file...
is there an reason? Is it better than "split" tables and indexes?