Cannot convert exp_channel_data to INNODB

I’m currently coming against an issue with a large EE2 site that I’ve recently moved to EC2/RDS. To take advantage of the RDS snapshots and not risk data-integrity issues (as per Amazon Recommendation) with the DB Snapshot/Backups, we need to convert all tables to INNODB.

The problem is that my exp_channel_data table is baulking with an error Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline..

All other tables converted fine. We have around 215+ custom fields across the entire site, so that means we've got around 430(ish) columns in the exp_channel_data table.

Anyone come across this or does anyone have advice on how to fix? Google suggests doing some my.cnf changes etc - but RDS doesn’t give me this (or console access), so I'm at a bit of a loss as to how I can sort this.

Looking at the datatypes of all the columns, none of them are particularly large - EE mostly creates fields with datatype of TEXT and TINYTEXT - but I have some in there with Decimals and/or INT.

Replay

Category: ee2 Time: 2016-07-29 Views: 0

Related post

iOS development

Android development

Python development

JAVA development

Development language

PHP development

Ruby development

search

Front-end development

Database

development tools

Open Platform

Javascript development

.NET development

cloud computing

server

Copyright (C) avrocks.com, All Rights Reserved.

processed in 0.146 (s). 12 q(s)