Update MySQL 5.1 to latest 5.6 version (1 Viewer)

[radical]

^ Your Link are ending in an error message for me.

 

[regeszter]

i attached script with ALTER there https://forum.team-mediaportal.com/threads/use-innodb-as-mysql-engine.114397/page-4#post-941725 (in case anyone wants to test this) - that was proved as working by many people

Error
You do not have permission to view this page or perform this action.

 

[Sebastiii]

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

 

[regeszter]

If some users can confirm to the alter table method is a working solution you can run that after upgrade process.

 

[azzuro]

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
Typeboolean
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).

 

[azzuro]

for use it, we need to switch to Baracuda instead of antelope and use Dynamic or compressed row format.

 

[FreakyJ]

Had the same error as Azzuro
You have to change some key sizes, but can't remember anymore in detail :/

 

[Sebastiii]

Fresh db is ok, i remember that some key are not ok 256 vs 255 etc.
So new new give is correct

 

[azzuro]

Yes ,
few table have 256 instead of 255, but what is the good number ???

 

[elliottmc]

So in theory if we do a clean install of MP, it will install MySQL 5.6 and use InnoDB ? And everything will be great?