<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Patchlog - Latest Comments in Repair a MySQL table</title><link>http://patchlog.disqus.com/</link><description></description><language>en</language><lastBuildDate>Tue, 06 Nov 2007 17:22:10 -0000</lastBuildDate><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803811</link><description>What a life saver !!!&lt;br&gt;This seems to be an issue when moving from V4-5 with large tables (I only had the issue on one table our of 40 I was migrating).&lt;br&gt;&lt;br&gt;I was getting the "table crashed error" but the "up to date" message when trying to do a MYSQL repair or a mysqlcheck on the table.  Based on the post, I ran the myisamchk (rather than USE_FRM on the repair cmd)... sweet !</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pita</dc:creator><pubDate>Tue, 06 Nov 2007 17:22:10 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803809</link><description>I'm glad to hear you solved the problem and thanks for following :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">symx</dc:creator><pubDate>Wed, 22 Aug 2007 03:44:55 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803810</link><description>Alright. You were right!&lt;br&gt;&lt;br&gt;Apparently when I repaired or restored the table...it really repaired the issue! I went back and piece by piece began editing pages. I was nervous and made a backup beforehand. It took!&lt;br&gt;&lt;br&gt;I really do need to edit the pages also because apparently upon repair or the restore [I am not sure which] it added a lot of ? [question marks] to random areas. I corrected the most recent posts of this.&lt;br&gt;&lt;br&gt;Thanks for all of your help. And now I am not scared to edit my posts thanks to your question. LoL...Still. I need to get my blog moved to the domain I got and update my WordPress.&lt;br&gt;&lt;br&gt;I am also now a member of your MyBlogLog community so I can &amp;lt;strike&amp;gt;stalk&amp;lt;/strike&amp;gt;  follow your blog. :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Samsara</dc:creator><pubDate>Tue, 21 Aug 2007 19:47:07 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803808</link><description>&lt;em&gt;I never heard of a table crash when editing a post before.&lt;/em&gt;&lt;br&gt;&lt;br&gt;Tell me about it!&lt;br&gt;&lt;br&gt;Let me give you the specs. WP 2.0.6 [Don't laugh! :P] I'll have to see if it happens again after restoring the table. It wasn't a "blog post" per se...but was a page off the parent. [This page: &lt;a href="http://samsara.ihostyou.com/recovery-hsp-resources/" rel="nofollow"&gt;Resources&lt;/a&gt;.] &lt;br&gt;&lt;br&gt;I needed to update some information. It may turn out whacked because I'm going in to test editing it to see if it yields a crash. If you watch you may be able to see it. ...oh and of course....when it crashes [although it references only the one table as being crashed and in need of repair...the entire site goes down and I get 404's sitewide.&lt;br&gt;&lt;br&gt;&lt;a href="http://samsara.ihostyou.com" rel="nofollow"&gt;http://samsara.ihostyou.com&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Samsara</dc:creator><pubDate>Mon, 20 Aug 2007 07:45:52 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803807</link><description>&lt;p&gt;I never heard of a table crash when editing a post before. what version are you using exactly? Maybe you could copy the same blog but create a new database and see if it still crashes. If it does then it's most likely a conflict between your mysql version and your wordpress version. If not then it may just be a problem with the database you repaired, in which case I would export it as SQL, delete it and then recreate it from SQL. Btw does this still happens after you restored the backup table?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">symx</dc:creator><pubDate>Mon, 20 Aug 2007 07:34:25 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803806</link><description>I used myisamchk because I did read time and time again from various tech -related resources that to use_frm was a baddie if you'd previously built your tables with one version and then got upgraded - which was my case.&lt;br&gt;&lt;br&gt;In my case I was built and contrived on mySQL 4 and then host went to v. 5. There was no issue until an edit. When I edited a page...it was like the Wordpress 'E bomb' exploded.&lt;br&gt;&lt;br&gt;I utilized your suggestion and all was well.&lt;br&gt;&lt;br&gt;Then I went back to edit again and again...it happened. This time no commands were working. I restored a backup table and that was a success. Currently my server tech's are looking into it. My version of WP is so old my grandmother was wearing black and white clothes when it came out...so I am thinking it's an incompatibility with mySQL 5 that's causing the original crashes.&lt;br&gt;&lt;br&gt;I'll keep you posted if you like. If other people find this nice post under similar circumstances they may be interested to hear any solution I find?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Samsara</dc:creator><pubDate>Mon, 20 Aug 2007 07:04:11 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803804</link><description>I'm glad to hear the post was helpful. Which suggestion did you try the one with USE_FRM or the one with myisamchk ?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">symx</dc:creator><pubDate>Fri, 17 Aug 2007 03:21:28 -0000</pubDate></item><item><title>Re: Repair a MySQL table</title><link>http://patchlog.com/databases/repair-a-mysql-table/#comment-2803805</link><description>This post saved my life. [Ironic you posted it on my birthday!]&lt;br&gt;&lt;br&gt;My server is in [was] in the middle of an upgrade from mySql 4 to mySQL 5. I like that you offer your own experience. I tried your suggestion and was successful. Now if I can just keep that table [wp_posts] from crashing everytime i try to now alter a post... hopefully the server's being worked on and it has to do with the upgrade though my mySQL knowledge is limited.&lt;br&gt;&lt;br&gt;Thanks for this. I Stumble thumbed it up! I'll be back! Fabulous.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Samsara</dc:creator><pubDate>Thu, 16 Aug 2007 21:49:03 -0000</pubDate></item></channel></rss>