Innodb multiple tablespace & unique name

[Andy]

I'm using Mysql Max-4.1.4-gamma for Linux.
I have a question related to a problem with my database server.
If on my db server I have 2 different database, say DB1 & DB2, I
create two INNODB tables with the same name (foo), one for each
database, how they are stored in the innodb data dictionary ?
DB1.foo & DB2.foo or simply foo ?

Thank you in advance

Andrea

[Heikki Tuuri]

Andy,

you should write to my***@lists.mysql.com. These newsgroups are mostly just
mirrors of mailing lists.

"Andy" <an****@hotmail.com> kirjoitti viestissä
news:95**************************@posting.google.c om...

I'm using Mysql Max-4.1.4-gamma for Linux.
I have a question related to a problem with my database server.
If on my db server I have 2 different database, say DB1 & DB2, I
create two INNODB tables with the same name (foo), one for each
database, how they are stored in the innodb data dictionary ?
DB1.foo & DB2.foo or simply foo ?
the name of the table in the InnoDB internal data dictionary is 'DB1/foo' or
'DB2/foo'.

The internal data dictionary is inside the ibdata1 file. Keep that in mind.
Do not move around table files manually:

http://dev.mysql.com/doc/mysql/en/Mu...blespaces.html
"
You cannot freely move `.ibd' files around between database directories the
way you can with MyISAM table files. This is because the table definition is
stored in the InnoDB shared tablespace, and also because InnoDB must
preserve the consistency of transaction IDs and log sequence numbers.
Within a given MySQL installation, you can move an `.ibd' file and the
associated table from one database to another with the familiar RENAME TABLE
statement:

RENAME TABLE old_db_name.tbl_name TO new_db_name.tbl_name;
"
Thank you in advance

Andrea

Best regards,

Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php