Bill Adams wrote:
InnoDB always needs the shared tablespace because it puts its
internal data dictionary and undo logs there. The .ibd files are
not sufficient for InnoDB to operate.
well, thats what I found before. But it doesn't explain why InnoDB
does need a logfile even when all tra
InnoDB always needs the shared tablespace because it puts its
internal data dictionary and undo logs there. The .ibd files are
not sufficient for InnoDB to operate.
well, thats what I found before. But it doesn't explain why InnoDB
does need a logfile even when all transactions are committ
Hello,
This is spelled out pretty clearly in the manual:
InnoDB always needs the shared tablespace because it puts its
internal data dictionary and undo logs there. The .ibd files are not
sufficient for InnoDB to operate.
well, thats what I found before. But it doesn't explain why InnoDB
On Mar 21, 2006, at 1:08 PM, Marten Lehmann wrote:
I had a lot of trouble today because the InnoDB integration in
MySQL is lousy. I read the manual and worked with
innodb_per_file_table. So when I shutdown mysql I should be able to
delete ib_logfile0, ib_logfile1 and ibdata1, because all ta
Marten Lehmann wrote:
I had a lot of trouble today because the InnoDB integration in MySQL
is lousy. I read the manual and worked with innodb_per_file_table. So
when I shutdown mysql I should be able to delete ib_logfile0,
ib_logfile1 and ibdata1, because all table-data should be stored in
th
Hi,
I had a lot of trouble today because the InnoDB integration in MySQL is
lousy. I read the manual and worked with innodb_per_file_table. So when
I shutdown mysql I should be able to delete ib_logfile0, ib_logfile1 and
ibdata1, because all table-data should be stored in the .idb and .frm
fi
