View Issue Details

IDProjectCategoryView StatusLast Update
09514DevelopmentSurvey editingpublic2026-11-20 23:44
ReporterDenisChenu Assigned To 
PrioritynormalSeverityminor 
Status acknowledgedResolutionopen 
Summary09514: Limiting SQL limit broken for big survey
Description

With big survey and a lot of multichoice, we can't activate survey due to survey size. We can do some optimization here.

Additional Information

Status in 7.11 (master):

  • 5 point choice and text display already use varchar(1).
  • Multiple choice (M, P) and the arrays A, B, C, E still use varchar(5).
  • Text display still has its own column.

Measured on MariaDB 10.11 (utf8mb4, row format dynamic), columns of one type per table:

  • InnoDB: 383 with varchar(5) (row size > 8126), 1016 with varchar(1) or an integer type.
  • MyISAM: 2884 in both cases, so no gain there.

Proposal for what is left:

  • varchar(1) for M, P, A, C, E and varchar(2) for B.
  • Only for newly activated surveys. Existing response tables are not altered.
  • No integer types and no removal of the text display column: both change how the rest of the code reads these fields.
TagsNo tags attached.

Users monitoring this issue

There are no users monitoring this issue.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2015-02-11 14:01 DenisChenu New Issue
2015-02-11 14:12 DenisChenu Additional Information Updated
2019-11-01 17:25 c_schmitz Category Survey design => Survey editing
2026-11-19 22:50 c_schmitz Status new => acknowledged
2026-11-20 23:43 c_schmitz Project Bug reports => Development
2026-11-20 23:43 c_schmitz Product Version 2.05 =>
2026-11-20 23:44 c_schmitz Additional Information Updated