Chris, InnoDB file format changes:
4.1.0 -> 4.1.1 introduced multiple tablespaces; 4.1.1 -> 4.1.2 or .3 allow multiple charsets in the same database installation (currently only the default charset is used in InnoDB); 5.0.0 -> 5.0.x create all new InnoDB tables in a space-saving format; this will also slightly change the InnoDB log format, and users of InnoDB Hot Backup should upgrade ibbackup at the same time. I hope there will not be more InnoDB file format changes in 2004 - 2005. In the MySQL tradition, an upgrade is always painless with no data conversion. But a downgrade is tricky if the file format has changed. Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL support from http://www.mysql.com/support/index.html ............. List:MySQL General Discussion« Previous MessageNext Message » From:Chris NolanDate:January 27 2004 1:29am Subject:InnoDB development Hi all, I've been away from the list for a while and am wondering if the following question has been answered: Given that the extremely funky InnoDB is going to gain a new file format in the future, would it be a fair guess to say that any additions to InnoDB requiring file format changes would be made after the release of the new compressed format? Regards, Chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
