View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
18614 | Bug reports | Installation | public | 2023-02-02 17:57 | 2023-06-08 18:35 |
Reporter | riqcles | Assigned To | c_schmitz | ||
Priority | none | Severity | minor | ||
Status | closed | Resolution | no change required | ||
Product Version | 5.5.x | ||||
Summary | 18614: lime_questions ERROR: Value '27373432210' is out of bounds for type integer at character 52 | ||||
Description | Hello, I did the following to select tables: select 'DROP TABLE ' AS constant1 , from information_schema.tables where table_catalog = 'limesurvey' This works fine, and generates the list of affected tables for me.... But looking at the log file, we see that errors on the selection of the lime_questions table are present: 2023-02-02 11:12:27.075 CET [28495] ERROR: Value '28815429493' is out of bounds for type integer at character 52 the value for each line (if I have sub questions) exceeds the limit of the number of characters for the type integer. Looking in more detail, I see that if in the code of the sub-question does not start with a letter (ex: SQ1) and that we only have numbers, the request will take the code of the sub-question which is a title, as the internal code of the subquestion. Users imported a template questionnaire, which contained sub-questions with only numbers, and as they have a lot of duplicate questionnaires (2000 lines of errors with the sub-questions), the processing time during the integrity check data, then cleaning (which crashes for me) takes a long time. | ||||
Steps To Reproduce | Create a quiz with an array question Run data integrity test. Go see the log on PostgreSQL server (or other). | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 2 | ||||
Complete LimeSurvey version number (& build) | Version 5.4.5+221010 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | Postgresql 13 | ||||
Server OS (if known) | |||||
Webserver software & version (if known) | |||||
PHP Version | 7.4.32 | ||||
related to | 16690 | acknowledged | Unable to use checkintegrity on big instance | |
related to | 17458 | closed | adamzammit | Check integrety broke with SQL error |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-02-02 17:57 | riqcles | New Issue | |
2023-02-02 17:57 | riqcles | File Added: sous_questions.png | |
2023-02-02 17:57 | riqcles | File Added: sous_questions_2.png | |
2023-02-02 17:57 | riqcles | File Added: sous_questions_3.png | |
2023-02-02 18:06 | DenisChenu | Relationship added | related to 16690 |
2023-02-02 18:07 | DenisChenu | Relationship added | related to 17458 |
2023-06-08 18:35 | c_schmitz | Note Added: 75494 | |
2023-06-08 18:35 | c_schmitz | Bug heat | 0 => 2 |
2023-06-08 18:35 | c_schmitz | Assigned To | => c_schmitz |
2023-06-08 18:35 | c_schmitz | Status | new => closed |
2023-06-08 18:35 | c_schmitz | Resolution | open => no change required |