Thanks for reporting the issue. Will raise the idea to have logs in the team.

In the meantime, can you provide further information? I would need:

1. The commit hash your LimeSurvey is on
2. Whether there were any custom changes
3. The full stack trace
4. Line 1471 is currently https://github.com/LimeSurvey/LimeSurvey/blob/151421a2f3629f54b27f9f7436bfb12a1e5ea75f/application/helpers/common_helper.php#L1471 which has no subtraction between string and int
5. What fieldname failed if any?

LimeSurvey Community Edition Version 7.0.0-beta1+260121
No custom changes on V7 (just extract , modify config.php, and run)

3. how I can do this ?

4. the full message :
   TypeError: Unsupported operand types: string - int in /var/www/html/limesurvey7/application/helpers/common_helper.php:1471
   Stack trace:
   #0 /var/www/html/limesurvey7/application/helpers/update/updates/Update_700.php(1074): getFieldName()
   #1 /var/www/html/limesurvey7/application/helpers/update/DatabaseUpdateBase.php(47): LimeSurvey\Helpers\Update\Update_700->up()
   #2 /var/www/html/limesurvey7/application/helpers/update/updatedb_helper.php(88): LimeSurvey\Helpers\Update\DatabaseUpdateBase->safeUp()
   #3 /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php(46): db_upgrade_all()
   #4 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
   #5 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
   #6 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
   #7 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()

5. I dont know, I do this :

[root@serveurIntranet httpd]# php /var/www/html/limesurvey7/application/commands/console.php updatedb
Update pgsql:host=serveurBdd;port=5432;user=limesurvey7;password=galileo;dbname=limesurvey7; with prefix :lime_ from 640 to 700
PHP Error[2]: Undefined array key 0
in file /var/www/html/limesurvey7/application/helpers/common_helper.php at line 1425
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(832): CErrorHandler->handle()
#1 /var/www/html/limesurvey7/application/helpers/common_helper.php(1425): ConsoleApplication->handleError()
#2 /var/www/html/limesurvey7/application/helpers/update/updates/Update_700.php(1074): getFieldName()
#3 /var/www/html/limesurvey7/application/helpers/update/DatabaseUpdateBase.php(47): LimeSurvey\Helpers\Update\Update_700->up()
#4 /var/www/html/limesurvey7/application/helpers/update/updatedb_helper.php(88): LimeSurvey\Helpers\Update\Update_700->safeUp()
#5 /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php(46): db_upgrade_all()
#6 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#7 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#8 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): ConsoleApplication->processRequest()
#9 /var/www/html/limesurvey7/application/commands/console.php(77): ConsoleApplication->run()
[root@serveurIntranet httpd]#

Thanks for the detailed answer. Before I get into the threads we opened, let me provide some general information. This is an old-ish version from January and we changed quite a lot since then. This is a newer version with lots of fixes:https://github.com/LimeSurvey/LimeSurvey/releases/tag/7.0.0-RC1%2B260430 . We are not logging issues as you correctly pointed out and I raised this idea in the team.

As about your responses:

1. Now, we had fundamental changes related to answers since January, we practically rewritten how ranking questions are to be handled, now they have subquestions rather than answers so it is no longer allowed to add/remove answers to an active survey. Why this was a problem and why it very well may be your issue. Imagine this scenario:

• you create a survey
• you create a ranking question
• you create some answers for it
• you activate the survey
• you remove some of the answers

What happens under the hood:

• your records in the {{answers}} table get removed
• your survey_<sid> table is not altered

So some fields representing some answers you removed are still in the responses table and the script attempts to convert them and finds no answer in the {{answers}} table to convert. (in current version it would be subquestion in the {{questions}} table). There could be other inconsistencies from some old tables that I cannot predict at this time.

So a way to solve it would be to count the answers of ranking questions versus fields in the responses table, like

select q.sid, count(*)
from lime_questions q
join lime_answers a
on q.qid = a.qid
group by q.sid, q.qid

vs.

select count(*)
from lime_questions q
join information_schema.columns c
on concat('limesurvey', q.sid) = c.TABLE_NAME AND
current_database() = 'your_database_name' and
COLUMN_NAME like concat(q.sid, 'X', q.gid, 'X', q.qid) AND
character_length(COLUMN_NAME) > character_length(concat(q.sid, 'X', q.gid, 'X', q.qid))

You can have these as subqueries and join by qid and a HAVING clause for the group by where the count(*) differs at the two sides. Those are potential issues. I presumed here your table prefix was lime_ . If it's something different, then you can adjust the queries.

In this version, line 1471 of common_helper.php is

$aid = $cd ? $index : $questions[0]->answers[(substr($fieldName, strlen("{$sid}X{$gid}X{$qid}")) - 1)]->aid;

and the two arrays potentially causing the problem are:

• $questions[0]
• $questions[0]->answers[(substr($fieldName, strlen("{$sid}X{$gid}X{$qid}")) - 1)]

and it is very likely that the {{answers}} table has not enough answers for the responses table to map to.

2. Thanks for clarifying.

3. In your 4. and 5. points you already did it, thank you.

$aid = $cd ? $index : $questions[0]->answers[((int)substr($fieldName, strlen("{$sid}X{$gid}X{$qid}")) - 1)]->aid;

may help as long as the substring ends up being numeric, but that's hacky, a newer version could be a better point of departure.

5. In the version you use, line 1425 is https://github.com/LimeSurvey/LimeSurvey/blob/68e30d06a8dabd9611c6c4cab16c1abe86e12de7/application/helpers/common_helper.php#L1425

$suffixText .= "_S" . $scales[$index];

and apparently there are no scales for $index, so your data is inconsistent there, but it's a different table.

I asked the team about logging, there is no decision yet.

If you wish to debug and log in the meantime, then here: https://github.com/LimeSurvey/LimeSurvey/blob/68e30d06a8dabd9611c6c4cab16c1abe86e12de7/application/helpers/update/updates/Update_700.php#L1119

You find

        try {
            $this->db->createCommand($scripts[$TABLE_NAME]['CREATE'])->execute();
            $this->db->createCommand($preinsert . $scripts[$TABLE_NAME]['INSERT'] . $postinsert)->execute();
            $this->db->createCommand($scripts[$TABLE_NAME]['DROP'])->execute();
        } catch (\Exception $ex) {
            if (strpos($TABLE_NAME, "old") !== false) {
                continue;
            } else {
                throw $ex;
            }
        }

you can do

        try {
            $this->db->createCommand($scripts[$TABLE_NAME]['CREATE'])->execute();
            $this->db->createCommand($preinsert . $scripts[$TABLE_NAME]['INSERT'] . $postinsert)->execute();
            $this->db->createCommand($scripts[$TABLE_NAME]['DROP'])->execute();
        } catch (\Exception $ex) {
            if (strpos($TABLE_NAME, "old") !== false) {
                continue;
            } else {
                echo $scripts[$TABLE_NAME]['CREATE'] . "<br><br>"; // use \n\n if you run it from the terminal
                throw $ex;
            }
        }

to see what table it attempted to create just before crashing. And then you can send that definition as well as the actual table structure in your database, note that we rename the tables, so your

{{survey_123456}} is renamed to {{responses_123456}}

and your

{{survey_123456_timings}} is renamed to {{timings_123456}}

Thank you for the information.

I'm not a developer, so it will be difficult for me to carry out all these steps.

As you indicated, it's probably old questionnaires and response tables that are causing the problem.

Since I can't run the integrity check (due to the data volume), there has been an accumulation of incorrect data (orphaned tables).

The scenario you described is entirely possible: I have several hundred managers who create dozens (or more) of questionnaires per week. It's impossible to keep track of them all :)

I think this bug can be fixed. It provides a starting point (and goodness knows you have plenty of work to do: thank you to the team) that we can address in a near-final version in September/October?

Otherwise, I modified my configuration to rerun the tests:
Still using Rocky 9.7, but I'm switching to:

• PHP 8.4.21 (cli) (built: May 5 2026 16:34:12) (NTS gcc x86_64)

• limesurvey7.0.0-RC1+260430

I'm increasing the file server memory from 2 GB to 16 GB.

(The database server remains at 2 GB and Postgres 17.7.)

I'm removing php-fpm to be as close as possible to my environments.

I modify the php.ini file by adding:

max_input_time = 300
memory_limit = 2048 M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE

I enable 'debug'=>2 in the config file.

And I rerun the update via the command line.

It's longer, but at the end this:

CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()

But I have the application.log file in the runtime which is more verbose: 20 MB
Example of a few lines:

2026/05/19 19:15:41 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42601]: Syntax error: 7 ERROR: zero-length delimited identifier at or near """"
LINE 36: "" character varying(5),

^. The SQL statement executed was: CREATE TABLE lime_old_responses_114533_2021020511460
//////////////////////
Or :
///////////////////////
2026/05/19 19:15:44 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE TABLE lime_old_responses_353872_20220113103614 (

I have this 6714 times in my file:
In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block.

I have attached the log file compressed with WinRAR.

Thank you for your response. The good news is that fixing this ranking behavior is approved and I'll do it today. We still did not get confirmation on whether we wish to do logs. The zero-length identifier is the empty fieldname in the create table statement. It's definitely the case in the ranking issue we discussed and that's gonna be fixed. It's also possible that some other issues with the symptoms may still exist, so with the fix I expect the number of this error at your end to be reduced to hopefully 0, but even a significant reduction would mean we removed this bug. We just don't know whether this is the last bug or not.

I have been pointed to https://bugs.limesurvey.org/view.php?id=19237

@lajosarpad : here, in my opinon, there are 2 issue we can try to fix

1. Have a way to check integrity by survey: I already think to create a plugin , but can be great to create some public function in https://github.com/LimeSurvey/LimeSurvey/blob/master/application/controllers/admin/CheckIntegrity.php (create function whete we have a foreach survey)
2. Better error return when SQL erro happen : CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51 replace by Syntax error: 7 ERROR: zero-length delimited identifier at or near """"

Your opinion ?

@DenisChenu thanks for the ideas, I'll notify the team about them. Personally I think 1. is a good idea as well as 2.

As per the change issue with rankings, we have a fix already merged into develop-major at https://github.com/LimeSurvey/LimeSurvey/pull/4985

Yes, i know :)

Did I report both issues: one for check integrity by survey + one for SQL error ?

I'm not sure whether they were reported separately, but I notified the team about both ideas.

Hello,
here's the continuation of the tests:

1. I downloaded the new version 7.0, available on limesurvey.org: limesurvey7.0.0+260526.zip

2. I used SQL scripts to delete all my OLD tables in the database (OLD_limesurvey and OLD_timings): I did not delete the OLD tables from the responses.

3. I reran the data integrity test through the application: this time, I received a message allowing me to delete the OLD tables that are no longer in use.

4. I performed an initial validation of this deletion, then reran the test, which indicated that there were still tables to delete.

5. I did not delete these tables and I reran the update using the command-line script.

6. Error message at the end of the script; I'm checking the generated log file.

7. Still this error message: [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42601]: Syntax error: 7 ERROR: zero-length delimited identifier at or near """"
   LINE 36: "" character varying(5),

^. The SQL statement executed was: CREATE TABLE lime_old_responses_114533_20210205114609

8. I rerun the integrity test and delete the remaining tables.

9. I rerun the script from the command line.

10. Error message at the end: I check the log file:
    2026/05/26 15:36:39 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[53200]: Out of memory: 7 ERROR: out of shared memory
    HINT: You might need to increase "max_locks_per_transaction".. The SQL statement executed was: DROP TABLE lime_old_survey_391629_20211019181545.

11. I modify my database server: increase to 4 GB of RAM, modification of the file by changing the value to 2048 MB and I restart the server.

12. I restart the script on the command line.

13. New error message:

2026/05/26 16:33:11 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42704]: Undefined object: 7 ERROR: index "lime_idx2_users" does not exist. The SQL statement executed was: DROP INDEX "lime_idx2_users".
2026/05/26 16:33:11 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE UNIQUE INDEX "lime_idx2_users" ON "lime_users" ("email").
2026/05/26 16:33:59 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}

14. WARNING: Actions on the web interface are performed on LimeSurvey Community Edition Version 6.17.3+260512

15. For this step:
    Data Redundancy Check

The redundancy check verifies the presence of tables left after deactivating questionnaires. You can delete them if you no longer need them.

I couldn't check all the boxes at once: I need to check 5,495 boxes to be able to click the <Clear checked items!> button.
This It would be nice to have a button to select them all and avoid using an SQL query.

16. I'm going to test it by deleting all the OLD_answer tables and running the script again.

2026/05/26 16:33:11 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42704]: Undefined object: 7 ERROR:  index "lime_idx2_users" does not exist. The SQL statement executed was: DROP INDEX "lime_idx2_users".
2026/05/26 16:33:11 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR:  current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE UNIQUE INDEX "lime_idx2_users" ON "lime_users" ("email").
2026/05/26 16:33:59 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---

sorry the name is lime_oldreponses not OLD_answer

Thanks for the detailed report. Can you test what the DB version is after running the change script?

You can find that out by running:

select stg_value from lime_settings_global where stg_name = 'DBVersion';

The result is 705.

In CLI :
[root@serveurIntranet html]# time php /var/www/html/limesurvey7/application/commands/console.php updatedb
Update pgsql:host=serveurBdd;port=5432;user=galileo;password=galileo;dbname=limesurvey7; with prefix :lime_ from 705 to 707
CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
real 0m23.284s
user 0m0.027s
sys 0m2.977s
I'm going to run the tests again because the database has been updated from version 705 to 707... and I still don't have access, as the script terminates with the error shown above on DROP INDEX:

I'm going to revert to the original database before the migration, then clean up all the OLD files, and then rerun the script from the command line (I'll also try a variation by running the update via the web interface).

Lots more testing to do :).

Thanks for the information! The great news is that 700 finally succeeded as well as 701, 702, 703, 704 and 705 and it crashed at 706 for you.

705 is about creating the react editor plugin and updating the priorities: https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updates/Update_705.php

706 is about deduplicating emails as we can see at https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updates/Update_706.php

The part which fails for you is:

    /**
     * Drop the existing non-unique index on email.
     */
    private function dropOldEmailIndex()
    {
        try {
            $this->db->createCommand()->dropIndex('{{idx2_users}}', '{{users}}');
        } catch (\Exception $e) {
            // Index may not exist in all installations.
        }
    }

however, the code catches any exception being thrown here in case you did not have the index. Can you confirm you have the same code for this function as above?

That's right, I started looking for the cause and I've come to the same conclusion:

and by using the web interface for the update (with debugging set to 1),

you can see the text below which indicates where the error is.

So, it's indeed the migration to 706 that causes the creation of this unique index for emails.

Why a DROP, since this data didn't exist before?

I reinstalled, creating a blank database from V7, and by looking at the users table, I see that the indexes are indeed created.

Here is the error text:

CDbException

CDbCommand could not execute the SQL command: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE UNIQUE INDEX "lime_idx2_users" ON "lime_users" ("email")

/var/www/html/limesurvey7/vendor/yiisoft/yii/framework/db/CDbCommand.php(358)

346 {
347 if($this->_connection->enableProfiling)
348 Yii::endProfile('system.db.CDbCommand.execute('.$this->getText().$par.')','system.db.CDbCommand.execute');
349
350 $errorInfo=$e instanceof PDOException ? $e->errorInfo: null;
351 $message=$e->getMessage();
352 Yii::log(Yii::t('yii','CDbCommand::execute() failed: {error}. The SQL statement executed was: {sql}.',
353 array('{error}'=>$message, '{sql}'=>$this->getText().$par)),CLogger::LEVEL_ERROR,'system.db.CDbCommand');
354
355 if(YII_DEBUG)
356 $message.='. The SQL statement executed was: '.$this->getText().$par;
357
358 throw new CDbException(Yii::t('yii','CDbCommand failed to execute the SQL statement: {error}',
359 array('{error}'=>$message)),(int)$e->getCode(),$errorInfo);
360 }
361 }
362
363 /*
364 Executes the SQL statement and returns query result.
365 This method is for executing an SQL query that returns result set.
366 @param array $params input parameters (name=>value) for the SQL execution. This is an alternative
367 to {@link bindParam} and {@link bindValue}. If you have multiple input parameters, passing
368 them in this way can improve the performance. Note that if you pass parameters in this way,
369 you cannot bind parameters or values ​​using {@link bindParam} or {@link bindValue}, and vice versa.
370 Please also note that all values ​​are treated as strings in this case, if you need them to be handled as

Stack Trace
#0

• /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/db/CDbCommand.php(1490): CDbCommand->execute()
  #1
  –
  /var/www/html/limesurvey7/application/helpers/update/updates/Update_706.php(145): CDbCommand->createIndex()

140)
141 ->execute();
142 station wagon;
143 default:
144 // MySQL and PostgreSQL allow multiple NULLs in unique indexes.
145 $this->db->createCommand()->createIndex(
146 '{{idx2_users}}',
147 '{{users}}',
148 'email',
149 true
150);

#2
–
/var/www/html/limesurvey7/application/helpers/update/updates/Update_706.php(24): LimeSurvey\Helpers\Update\Update_706->createUniqueEmailIndex()

19 public function up()
20 {
21 $this->convertEmptyEmailsToNull();
22 $this->duplicateEmails();
23 $this->dropOldEmailIndex();
24 $this->createUniqueEmailIndex();
25 }
26
27 /*
28 Convert empty email strings to NULL.
29 */

#3
–
/var/www/html/limesurvey7/application/helpers/update/DatabaseUpdateBase.php(47): LimeSurvey\Helpers\Update\Update_706->up()

42 */
43 public function safeUp()
44 {
45 $transaction = $this->db->beginTransaction();
46 try {
47 $this->up();
48 $this->updateVersion();
49 $transaction->commit();
50 } catch (Throwable $e) {
51 $transaction->rollback();
52 throw $e;

#4

• /var/www/html/limesurvey7/application/helpers/update/updatedb_helper.php(119): LimeSurvey\Helpers\Update\DatabaseUpdateBase->safeUp()
  #5

• /var/www/html/limesurvey7/application/controllers/AdminController.php(166): db_upgrade_all()
  #6

• /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/web/CWebApplication.php(282): AdminController->run()
  #7

• /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/web/CWebApplication.php(141): CWebApplication->runController()
  #8

• /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CWebApplication->processRequest()
  #9

• /var/www/html/limesurvey7/index.php(161): CApplication->run()

The reason for needing the drop is that it was created for some installations. The reasoning is that if it fails, we need to silently ignore it, because it was not created in the first place. The solution I would do if I was to administer your PostgreSQL RDBMS would be to manually add the key by that name to the table, so when it attempts to drop it, it will succeed instead of throwing an error and possibly reestablishing connection. Unfortunately I can only guess about the exact details that you have, but I do think this approach would help, it's at least worth a try. If this solves the issue for you, then we'll need to fix this script to check for the existence of the index before attempting to drop it.

Thanks a lot for your patience.

@tibor.pacalat, can we have a developer look into this?

@Mazi I will check what is the status of this.

@lajosarpad

Unfortunately I can only guess about the exact details that you have, but I do think this approach would help, it's at least worth a try. If this solves the issue for you, then we'll need to fix this script to check for the existence of the index before attempting to drop it.

In one of my plugins, I don't find a way to check if an index exists: https://gitlab.com/SondagesPro/coreAndTools/reloadAnyResponse/-/blob/master/reloadAnyResponse.php?ref_type=heads#L1590
I just do a try/cast

You can differentiate between the drivers that are used for the supported RDBMS (MySQL/MariaDB, PostgreSQL or SQL Server) and have the appropriate SQL being executed.

Okay, testing is complete.

1. I reloaded the original database (V6).

2. I modified the database (V6) by adding indexes (see attached file) with the issues described in the attached files.

3. I deleted all the OLD tables:

SELECT
CONCAT('DROP TABLE ', table_name, ' CASCADE ;') AS drop_instruction

FROM information_schema.tables,

generate_series(2011, 2024) AS annee -- Generates the years from 2011 to 2024

WHERE table_catalog = 'limesurveyv7'

AND table_schema = 'public'

AND table_type = 'BASE TABLE'

AND table_name ~ ('^lime_oldresponses[0-9]+_' || annee || '[0-9]{10}$')

or table_name ~ ('^lime_oldtokens[0-9]+_' || annee || '[0-9]{10}$')

or table_name ~ ('^lime_oldsurvey[0-9]+_' || year || '[0-9]{10}$')

ORDER BY table_name;

4. I re-ran the migration script from the command line

5. [root@serveurIntranet ~]# time php /var/www/html/limesurvey7/application/commands/console.php updatedb
   Update pgsql:host=serveurBdd;port=5432;user=limesurvey;password=limesurvey;dbname=galileov7; with prefix :lime_ from 623 to 707
   Database has been successfully upgraded to version 707

real 11m15.607s
user 0m9.506s
sys 2m54.471s
[root@serveurIntranet ~]#

So it works.

But keep in mind that some people might be experiencing the same issue as me.

Question: I didn't have indexes with idx2 in previous versions (as you can see in the attachments). After the migration, the other indexes haven't changed (no idx, just the old names from the screenshot).

P.S.: I have another bug in the new editor:

------------ The new editor is currently only compatible with the 'Fruity TwentyThree' theme and is displayed each time a questionnaire is selected.

------------ And if I select one of the menus on the left (e.g., General), I get a "checking permission" message that keeps running for a long time.

Perhaps it's related to my database size...

I'll check if others have reported this before doing so.

2026-05-29_index_1.png (26,979 bytes)   

2026-05-29_index_1.png (26,979 bytes)   

2026-05-29_index_2.png (27,399 bytes)   

2026-05-29_index_2.png (27,399 bytes)   

2026-05-29_index_3.png (25,603 bytes)   

2026-05-29_index_3.png (25,603 bytes)   

2026-05-29_index_4.png (30,938 bytes)   

2026-05-29_index_4.png (30,938 bytes)   

I restarted the process:
Starting with a sizable V6 database

1. Adapt the data integrity cleanup script to remove the old tables (see: )

2. Verify with the SQL command that the tables are no longer present.

3. Enable debug mode and log file generation

4. Run the script in CLI mode.

The migration from version 651 to 708 stops with the following message:

CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51

I have attached the generated log file.

Note: I have the following permissions with the limesurveyV7 user of the database to be migrated: Create Role, Database, Can log in.

I'm retesting with the Postgres user (not good :( ) who is superuser.

I haven't added the index creation (as seen previously).

I think this will work, but what permission is the limesurveyV7 user missing, given that my previous migrations didn't require any privilege escalation?

Well, it didn't work because I'm still getting the lime_idx2_users message, so I'm going to create it again and run the script again.

Okay, we're making progress: database migration error from 705 to 708.
...oh dear, I forgot to save my index. Let's start again.

Okay, this time it's working.

But what about the database user?

the file

2026/06/17 16:23:35 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42501]: Insufficient privilege: 7 ERROR:  permission denied for schema public. The SQL statement executed was: 
                CREATE OR REPLACE FUNCTION show_create_table(table_name text, join_char text = E'
' ) 
                  RETURNS text AS 
                $BODY$
                SELECT 'CREATE TABLE ' || $1 || ' (' || $2 || '' || 
                    string_agg(column_list.column_expr, ', ' || $2 || '') || 
                    '' || $2 || ');'
                FROM (
                  SELECT '    "' || column_name || '" ' || data_type || 
                       coalesce('(' || character_maximum_length || ')', '') || 
                       case when is_nullable = 'YES' then '' else ' NOT NULL' end as column_expr
                  FROM information_schema.columns
                  WHERE table_schema = 'public' AND table_name = $1
                  ORDER BY ordinal_position) column_list;
                $BODY$
                  LANGUAGE SQL STABLE
                ;
                .
2026/06/17 16:23:56 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---
2026/06/17 16:31:34 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42501]: Insufficient privilege: 7 ERROR:  permission denied for schema public. The SQL statement executed was: 
                CREATE OR REPLACE FUNCTION show_create_table(table_name text, join_char text = E'
' ) 
                  RETURNS text AS 
                $BODY$
                SELECT 'CREATE TABLE ' || $1 || ' (' || $2 || '' || 
                    string_agg(column_list.column_expr, ', ' || $2 || '') || 
                    '' || $2 || ');'
                FROM (
                  SELECT '    "' || column_name || '" ' || data_type || 
                       coalesce('(' || character_maximum_length || ')', '') || 
                       case when is_nullable = 'YES' then '' else ' NOT NULL' end as column_expr
                  FROM information_schema.columns
                  WHERE table_schema = 'public' AND table_name = $1
                  ORDER BY ordinal_position) column_list;
                $BODY$
                  LANGUAGE SQL STABLE
                ;
                .
2026/06/17 16:31:56 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---
2026/06/17 16:44:13 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[53200]: Out of memory: 7 ERROR:  out of shared memory
HINT:  You might need to increase "max_locks_per_transaction".. The SQL statement executed was: CREATE TABLE lime_responses_265375 (
    "id" serial PRIMARY KEY, 
    "submitdate" timestamp without time zone, 
    "lastpage" integer, 
    "startlanguage" character varying(20) NOT NULL, 
    "seed" character varying(31), 
    "startdate" timestamp without time zone NOT NULL, 
    "datestamp" timestamp without time zone NOT NULL, 
    "Q387650" timestamp without time zone, 
    "Q387651" text, 
    "Q387637" character varying(5), 
    "Q387638" character varying(5), 
    "Q387639" character varying(5), 
    "Q387640" text, 
    "Q387652" text, 
    "Q387644" character varying(5), 
    "Q387642" character varying(5), 
    "Q387643" character varying(5), 
    "Q387646" character varying(5), 
    "Q387657" character varying(5), 
    "Q387645" character varying(5), 
    "Q387653" character varying(5), 
    "Q387678" character varying(5), 
    "Q387654" character varying(5), 
    "Q387661" text, 
    "Q387662" text, 
    "Q387660" text, 
    "Q387655" character varying(5), 
    "Q387658" character varying(5), 
    "Q387656" character varying(5), 
    "Q387659" character varying(5), 
    "Q387648" character varying(5), 
    "Q387649" character varying(5)
);.
2026/06/17 16:44:37 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---
2026/06/17 17:02:46 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42704]: Undefined object: 7 ERROR:  index "lime_idx2_users" does not exist. The SQL statement executed was: DROP INDEX "lime_idx2_users".
2026/06/17 17:02:46 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR:  current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE UNIQUE INDEX "lime_idx2_users" ON "lime_users" ("email").
2026/06/17 17:03:14 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---
2026/06/17 17:06:18 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[42704]: Undefined object: 7 ERROR:  index "lime_idx2_users" does not exist. The SQL statement executed was: DROP INDEX "lime_idx2_users".
2026/06/17 17:06:18 [error] [system.db.CDbCommand] CDbCommand::execute() failed: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR:  current transaction is aborted, commands ignored until end of transaction block. The SQL statement executed was: CREATE UNIQUE INDEX "lime_idx2_users" ON "lime_users" ("email").
2026/06/17 17:06:39 [error] [exception.CException] CException: Please fix this error in your database and try again in /var/www/html/limesurvey7/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /var/www/html/limesurvey7/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /var/www/html/limesurvey7/application/commands/console.php(77): CApplication->run()
#4 {main}
---