Issue Bug Closed

#108457Table tx_scheduler_task column selected_tables too short for OptimizeDatabaseTableTask

Tobias Jungmann 12/10/25, 06:22 updated 03/31/26, 08:59

Description

Problem: The table tx_scheduler_task has the data type VARCHAR(255).

This leads to SQL error: "An exception occurred while executing a query: Data too long for column 'selected_tables' at row 1" when selecting too many tables in the OptimizeDatabaseTableTask.

It’s not a big deal as I can setup multiple of those tasks but it’s not an optimal UX.

Reviews 1

History 56

  1. Tobias Jungmann commented <span data-processor="relativetime" data-value="2025-12-10T06:24:54+00:00" > 12/10/25, 06:24 </span>

    It would also be nice to have a best practise guide for that task. Which tables? How often? When?

  2. Garvin Hicking commented <span data-processor="relativetime" data-value="2025-12-10T14:34:53+00:00" > 12/10/25, 14:34 </span>

    Tobias Jungmann wrote in #note-1:
    > It would also be nice to have a best practise guide for that task. Which tables? How often? When?

    Thanks for your report! A patch now adjusts this. BTW: You can also create an `ext_tables.sql` file in your own extension/sitepackage and enlarge the database field on your own, if you need a solution quickly.

    You can optimize database tables that frequently receive new entries and old entries are removed, so that depends on your usage scenario. This would also be a seperate task/issue, probably more for documentation rather than the core.

  3. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-12-11T08:10:09+00:00" > 12/11/25, 08:10 </span>

    Applied in changeset commit:87f28987550d9e8e8e65eb337bb40219af84faaf.