Project

General

Profile

Actions
Copy link

Bug #4946

closed

InnoDB row size limit hit with textarea and editor fieldtypes

Added by krileon over 10 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
High
Assignee:
beat
Target version:
-
Start date:
16 December 2014
Due date:
% Done:

100%

Estimated time:

Description

Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

The above is output when attempting to convert to InnoDB when textarea or editor fieldtypes contain a very large amount of information. For example 10+ paragraphs.

https://www.joomlapolis.com/forum/153-professional-member-support/227677-error-1118-error-upgrading-from-cb-19-to-cb-204#255019

Actions
Copy link
 #1

Updated by krileon over 10 years ago

Confirmed locally with users site data. Issue does not appear configuration or host related.

Actions
Copy link
 #2

Updated by krileon over 10 years ago

Changing the mediumtext columns to text had no affect in resolving the issue.

Actions
Copy link
 #3

Updated by krileon over 10 years ago

Completely emptying the table of all rows allowed the Engine to be changed to InnoDB.

Actions
Copy link
 #4

Updated by beat about 10 years ago

  • Target version changed from CB 2.0.5 to CB 2.0.6
Actions
Copy link
 #5

Updated by beat about 10 years ago

  • Target version changed from CB 2.0.6 to CB 2.0.7
Actions
Copy link
 #6

Updated by beat about 10 years ago

  • Target version changed from CB 2.0.7 to CB 2.0.8
Actions
Copy link
 #7

Updated by beat almost 10 years ago

  • Target version changed from CB 2.0.8 to CB 2.0.9
Actions
Copy link
 #8

Updated by beat almost 10 years ago

  • Target version changed from CB 2.0.9 to CB 2.0.10
Actions
Copy link
 #9

Updated by beat over 9 years ago

  • Target version changed from CB 2.0.10 to CB 2.0.11
Actions
Copy link
 #10

Updated by beat over 9 years ago

  • Target version changed from CB 2.0.11 to CB 2.0.12
Actions
Copy link
 #11

Updated by beat over 9 years ago

  • Target version changed from CB 2.0.12 to CB 2.0.13
Actions
Copy link
 #12

Updated by beat about 9 years ago

  • Target version changed from CB 2.0.13 to CB 2.0.14
Actions
Copy link
 #13

Updated by beat about 9 years ago

  • Target version changed from CB 2.0.14 to CB 2.0.15
Actions
Copy link
 #14

Updated by beat over 8 years ago

  • Target version changed from CB 2.0.15 to CB 2.1
Actions
Copy link
 #15

Updated by krileon over 8 years ago

  • Target version changed from CB 2.1 to CB 2.2
Actions
Copy link
 #16

Updated by krileon almost 7 years ago

  • Target version changed from CB 2.2 to CB 2.8
Actions
Copy link
 #17

Updated by krileon about 3 years ago

  • 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.

Actions
Copy link

Also available in: Atom PDF