Hello, Just a quick question to see if anyone's tried this and run into any problems, or if it'll even work - I have a *huge* table that's just crashed thanks to FreeBSD panicking, and the repair operation I'm estimating is going to be another 4 hours :(
But anyway, I'm pondering over splitting this table up into a few sub-tables then making the change transparent to overlying code via a MERGE table. The data in this table is inserted hourly, and once it's in there, it doesn't change until I delete it 25 days later. It's kind of a rolling database. I've mused over the idea of making one MyISAM table for each day, creating a new one every night, and updating the MERGE schema - this also means I don't have to do a time consuming DELETE of old data - I just take the table definition out of the MERGE, move the datafile away so MySQL can't see it, and flush-tables. Now that's all well and good and I'm fairly sure it'll all work, but another interesting idea I was wondering over was - can I myisampack the tables that I know won't be updated anymore, and still MERGE them, with other unpacked-tables? Sorry, this got a bit long and rambly :) -- Chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
