Update MySQL 5.1 to latest 5.6 version (1 Viewer)

radical

Portal Pro
December 16, 2010
1,466
191
Home Country
Germany Germany
^ Your Link are ending in an error message for me.
 

Sebastiii

Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    Yep i understand but the whole point is to adapt that into DeployTools and it's here i'm not sure if i can or able to do that.
    So i prefer to keep it like this :) or if someone can help on it lol.
    I attach the script from Permission thread :)
     

    Attachments

    • MySQL2InnoDB.zip
      967 bytes

    regeszter

    Retired Team Member
  • Premium Supporter
  • October 29, 2005
    5,335
    4,954
    Home Country
    Hungary Hungary
    If some users can confirm to the alter table method is a working solution you can run that after upgrade process.
     

    azzuro

    Test Group
  • Team MediaPortal
  • May 10, 2007
    9,948
    5,617
    France - IDF
    Home Country
    France France
    for me, not working for all table.
    few table have more than 255 character for VARCHAR collumn ,
    if i remember was scheduled / recording, and one more.

    http://dev.mysql.com/doc/refman/5.6/en/innodb-restrictions.html
    http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_large_prefix
    we should set ON innodb_large_prefix
    innodb_large_prefix
    Introduced5.6.3
    Command-Line Format--innodb_large_prefix
    Option-File Formatinnodb_large_prefix
    System Variable Nameinnodb_large_prefix
    Variable ScopeGlobal
    Dynamic VariableYes
    Permitted Values
    Type
    boolean
    DefaultOFF
    Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes), for InnoDB tables that use the DYNAMIC and COMPRESSED row formats. (Creating such tables also requires the option values innodb_file_format=barracuda and innodb_file_per_table=true.) See Section 14.2.7, “Limits on InnoDB Tables” for the relevant maximums associated with index key prefixes under various settings.

    For tables using the REDUNDANT and COMPACT row formats, this option does not affect the allowed key prefix length. It does introduce a new error possibility. When this setting is enabled, attempting to create an index prefix with a key length greater than 3072 for a REDUNDANT or COMPACT table causes an error ER_INDEX_COLUMN_TOO_LONG (1727).
     

    FreakyJ

    Retired Team Member
  • Premium Supporter
  • July 25, 2010
    4,024
    1,420
    Home Country
    Germany Germany
    Had the same error as Azzuro
    You have to change some key sizes, but can't remember anymore in detail :/
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    Fresh db is ok, i remember that some key are not ok 256 vs 255 etc.
    So new new give is correct :)
     

    azzuro

    Test Group
  • Team MediaPortal
  • May 10, 2007
    9,948
    5,617
    France - IDF
    Home Country
    France France
    Yes ,
    few table have 256 instead of 255, but what is the good number ???
     

    Users who are viewing this thread

    Top Bottom