SQL Error

  • Tobias Bohwalli

    (@tobias-bohwalli)


    15 years ago

    WordPress database error The used table type doesn’t support FULLTEXT indexes for query CREATE FULLTEXT INDEX post_related ON wp_posts(post_title,post_content); made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, saq_wpseotags_DBSetup

Viewing 5 replies - 1 through 5 (of 5 total)
  • s_ha_dum

    (@apljdi)

    15 years ago

    I’ve made a FULLTEXT index on post_title,post_content,post_excerpt with no problem, that makes me think you’ve got a server configuration issue.

    Thread Starter Tobias Bohwalli

    (@tobias-bohwalli)

    15 years ago

    Version 3.1.3 installed all default tables as InnoDB which do not support fulltext.

    s_ha_dum

    (@apljdi)

    15 years ago

    I just installed a brand new, freshly downloaded WordPress 3.1.3 yesterday and the tables are all MyISAM. InnoDB is available on my SQL server so it could have been used if WP wanted it.

    Thread Starter Tobias Bohwalli

    (@tobias-bohwalli)

    15 years ago

    Interesting, i did installed it yesterday to, maybe you should just apply a db check and notice or ALTER function so nobody else assume the plugin is broken (it seems to be a popular plugin so many may encounter the same issue). InnoDB is mainly useful if WP uses commit, rollback and foreign keys, have not checked if it does. Percona mysql seems to build strict on InnoDB.

    s_ha_dum

    (@apljdi)

    15 years ago

    I’m not really in any position to “apply a db check” or anything else, as it isn’t my plugin.

    Your problem has something to do with Percona? Is that what you mean?

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

The topic ‘SQL Error’ is closed to new replies.

  • 5 replies
  • 2 participants
  • Last reply from: s_ha_dum
  • Last activity: 15 years ago
  • Status: not resolved