Title: SQL fixup fail
Last modified: August 20, 2016

---

# SQL fixup fail

 *  Resolved [mippie32](https://wordpress.org/support/users/mippie32/)
 * (@mippie32)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/)
 * I noticed the fix/workaround included in the latest version probably doesnt work
   as this message keeps coming back. Not a real issue for me (as everything works
   now ;-)) But FYI
 * Diag keeps giving this everytime
 * Post Deletion 2013-02-09 11:31:33 SQL Fixup : Alter table wp_wordbooker_fb_friends
   ADD FULLTEXT INDEX name_idx (name); –
    Post Deletion 2013-02-09 11:31:33 SQL 
   Fixup Fail : The used table type doesn’t support FULLTEXT indexes –
 * [http://wordpress.org/extend/plugins/wordbooker/](http://wordpress.org/extend/plugins/wordbooker/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Steve](https://wordpress.org/support/users/steveatty/)
 * (@steveatty)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/#post-3452684)
 * You’ve got your default DB table type set to INNODB at a guess and INNODB doesn’t
   support fulltext indexes.
 *  Thread Starter [mippie32](https://wordpress.org/support/users/mippie32/)
 * (@mippie32)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/#post-3452688)
 * OK. And yes, thats correct.
    I altered the wordbooker tables.
 * ALTER TABLE wp_wordbooker_errorlogs ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_fb_friends
   ENGINE=MyISAM; ALTER TABLE wp_wordbooker_fb_friend_lists ENGINE=MyISAM; ALTER
   TABLE wp_wordbooker_postcomments ENGINE=MyISAM; ALTER TABLE wp_wordbooker_postlogs
   ENGINE=MyISAM; ALTER TABLE wp_wordbooker_process_queue ENGINE=MyISAM; ALTER TABLE
   wp_wordbooker_userdata ENGINE=MyISAM; ALTER TABLE wp_wordbooker_userstatus ENGINE
   =MyISAM;
 * But it is a little funny I think, isnt it common to use the innodb as engine 
   for WP tables? ( [http://www.dev4press.com/2011/tutorials/wordpress/practical/choosing-mysql-database-engine-myisam-or-innodb/](http://www.dev4press.com/2011/tutorials/wordpress/practical/choosing-mysql-database-engine-myisam-or-innodb/))
   ==> When I google around I only see people switching to innodb as engine?
 * Anyway, it worked out, thanks.
 *  Plugin Author [Steve](https://wordpress.org/support/users/steveatty/)
 * (@steveatty)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/#post-3452713)
 * The only table that needs to be MyISAM is the friends list. The rest of them 
   can be InnoDB so I’ve changed the table create script to specifically state it
   for that table and the fix up code now checks for storage on tables and will 
   usually leave them alone.
 * I suspect most people on single blogs wont notice the differences between the
   two normally.
 *  Thread Starter [mippie32](https://wordpress.org/support/users/mippie32/)
 * (@mippie32)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/#post-3452720)
 * Great 🙂

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘SQL fixup fail’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordbooker.svg)
 * [Wordbooker](https://wordpress.org/plugins/wordbooker/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordbooker/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordbooker/)
 * [Active Topics](https://wordpress.org/support/plugin/wordbooker/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordbooker/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordbooker/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [mippie32](https://wordpress.org/support/users/mippie32/)
 * Last activity: [13 years, 4 months ago](https://wordpress.org/support/topic/sql-fixup-fail/#post-3452720)
 * Status: resolved