[BUGFIX] Enlarge scheduler object DB field 53/58953/2
authorBenni Mack <benni@typo3.org>
Mon, 26 Nov 2018 14:51:45 +0000 (15:51 +0100)
committerMarkus Klein <markus.klein@typo3.org>
Mon, 26 Nov 2018 16:25:01 +0000 (17:25 +0100)
The serialized PHP object is stored within the database field
"serialized_task_object". When serializing this could lead to several
issues.

One particular issue is that the object has lots of data or dependencies,
it cannot be stored at all in this database field.

Although we know that this implementation detail of scheduler is a rather
bad idea, we can only fix this by enlarging the field from "blob" to
"mediumblob" for now.

Resolves: #87006
Releases: master, 8.7
Change-Id: I2b335f258fe18b494033bde28eff76f2e67d34bb
Reviewed-on: https://review.typo3.org/58953
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Riny van Tiggelen <info@online-gamer.nl>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Markus Klein <markus.klein@typo3.org>
Tested-by: Markus Klein <markus.klein@typo3.org>
typo3/sysext/scheduler/ext_tables.sql

index 7bdbf98..36b73ce 100644 (file)
@@ -11,8 +11,8 @@ CREATE TABLE tx_scheduler_task (
        lastexecution_time int(11) unsigned DEFAULT '0' NOT NULL,
        lastexecution_failure text,
        lastexecution_context char(3) DEFAULT '' NOT NULL,
-       serialized_task_object blob,
-       serialized_executions blob,
+       serialized_task_object mediumblob,
+       serialized_executions mediumblob,
        task_group int(11) unsigned DEFAULT '0' NOT NULL,
        PRIMARY KEY (uid),
        KEY index_nextexecution (nextexecution)