Bug #4946
closed
Confirmed locally with users site data. Issue does not appear configuration or host related.
Changing the mediumtext columns to text had no affect in resolving the issue.
Completely emptying the table of all rows allowed the Engine to be changed to InnoDB.
- Target version changed from CB 2.0.5 to CB 2.0.6
- Target version changed from CB 2.0.6 to CB 2.0.7
- Target version changed from CB 2.0.7 to CB 2.0.8
- Target version changed from CB 2.0.8 to CB 2.0.9
- Target version changed from CB 2.0.9 to CB 2.0.10
- Target version changed from CB 2.0.10 to CB 2.0.11
- Target version changed from CB 2.0.11 to CB 2.0.12
- Target version changed from CB 2.0.12 to CB 2.0.13
- Target version changed from CB 2.0.13 to CB 2.0.14
- Target version changed from CB 2.0.14 to CB 2.0.15
- Target version changed from CB 2.0.15 to CB 2.1
- Target version changed from CB 2.1 to CB 2.2
- Target version changed from CB 2.2 to CB 2.8
- Status changed from Assigned to Rejected
- Target version deleted (
CB 2.8)
- % Done changed from 0 to 100
Not really an issue anymore. This can happen with Innodb installs with legacy defaults that have not been updated. There's nothing we specifically can do about it as is a MySQL configuration problem.
Also available in: Atom
PDF