Upgrade Error: 3.8.4 pl2 to 4.0.1 Suite - mysql error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kontrabass
    Senior Member
    • Jul 2000
    • 302
    • 3.6.x

    #31
    Originally posted by aa7bq
    Same problem here. The easy fix (for me) was to use MyIsam instead of Innodb. The change is easy.

    In the file: install/functions_installupgrade.php

    find the function get_high_concurrency_table_engine($db)

    Just add this line at the top of the function:


    return 'MyISAM';

    This way, InnoDB is never chosen.

    Once I did this, all of the problems described in this thread went away.
    Thanks for the tip, but what if we want InnoDB for high concurrency tables? I can change table engines with no problem in phpMyAdmin, so perhaps someone could post a list of all tables that should be InnoDB?

    Comment

    • StevenTN
      Senior Member
      • Mar 2002
      • 123
      • 4.2.X

      #32
      Trevor: The problem is traced to an improperly deleted InnoDB table (usually due to a botched upgrade in the past). InnoDB is a pain in the rear, and would result in errors that you so describe. I know this from being involved with MySQL for so long.
      Proud Admin of http://www.thrillnetwork.com/
      Finally live with vB4... I will say it's a pain in the bucket compared to what we're used to working with (using free CMS software no less).
      "If it doesn't fit, beat it with a hammer until it does"
      - Jesse James, West Coast Choppers

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...