Project

General

Profile

Actions

Bug #104319

closed

SQLite Install TYPO3v13: sys_reactions and sys_webhook create endless DB Analyzer cycle

Added by Garvin Hicking 5 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2024-07-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Setting up a fresh TYPO3 v13.2 install with SQLite and all core extensions including webhook+reactions, there is an endless loop in the DB Analyzer. It always tries to recreate the same structure over and over again, apoarantly because the Schema is recognized as being different.

Applying the changes works without a reported error message.

This is the list the Analyzer reports:

 CREATE TEMPORARY TABLE __temp__sys_reaction AS SELECT uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, impersonate_user, storage_pid, reaction_type, name, identifier, secret, table_name, fields FROM "sys_reaction" 
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
DROP TABLE "sys_reaction" 
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE TABLE "sys_reaction" (uid INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, updatedon INTEGER UNSIGNED DEFAULT 0 NOT NULL, createdon INTEGER UNSIGNED DEFAULT 0 NOT NULL, deleted SMALLINT UNSIGNED DEFAULT 0 NOT NULL, disabled SMALLINT UNSIGNED DEFAULT 0 NOT NULL, starttime INTEGER UNSIGNED DEFAULT 0 NOT NULL, endtime INTEGER UNSIGNED DEFAULT 0 NOT NULL, description CLOB DEFAULT NULL COLLATE "BINARY", impersonate_user INTEGER UNSIGNED DEFAULT 0 NOT NULL, storage_pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, reaction_type VARCHAR(255) DEFAULT '' NOT NULL COLLATE "BINARY", name VARCHAR(100) DEFAULT '' NOT NULL COLLATE "BINARY", identifier VARCHAR(36) DEFAULT '' NOT NULL COLLATE "BINARY", secret VARCHAR DEFAULT '' NOT NULL COLLATE "BINARY", table_name VARCHAR(255) DEFAULT '' NOT NULL COLLATE "BINARY", "fields" CLOB DEFAULT NULL)
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
INSERT INTO "sys_reaction" (uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, impersonate_user, storage_pid, reaction_type, name, identifier, secret, table_name, "fields") SELECT uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, impersonate_user, storage_pid, reaction_type, name, identifier, secret, table_name, fields FROM __temp__sys_reaction
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
DROP TABLE __temp__sys_reaction
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE INDEX parent_1708c523 ON "sys_reaction" (pid, deleted, disabled)
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE INDEX index_source_7c0d7594 ON "sys_reaction" (reaction_type)
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE UNIQUE INDEX identifier_key_643a6403 ON "sys_reaction" (identifier)
Current value: "fields" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE TEMPORARY TABLE __temp__sys_webhook AS SELECT uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, webhook_type, name, identifier, secret, url, method, verify_ssl, additional_headers FROM "sys_webhook" 
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
DROP TABLE "sys_webhook" 
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE TABLE "sys_webhook" (uid INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, updatedon INTEGER UNSIGNED DEFAULT 0 NOT NULL, createdon INTEGER UNSIGNED DEFAULT 0 NOT NULL, deleted SMALLINT UNSIGNED DEFAULT 0 NOT NULL, disabled SMALLINT UNSIGNED DEFAULT 0 NOT NULL, starttime INTEGER UNSIGNED DEFAULT 0 NOT NULL, endtime INTEGER UNSIGNED DEFAULT 0 NOT NULL, description CLOB DEFAULT NULL COLLATE "BINARY", webhook_type VARCHAR(255) DEFAULT '' NOT NULL COLLATE "BINARY", name VARCHAR(100) DEFAULT '' NOT NULL COLLATE "BINARY", identifier VARCHAR(36) DEFAULT '' NOT NULL COLLATE "BINARY", secret VARCHAR DEFAULT '' NOT NULL COLLATE "BINARY", url CLOB DEFAULT '' NOT NULL COLLATE "BINARY", method VARCHAR(10) DEFAULT '' NOT NULL COLLATE "BINARY", verify_ssl SMALLINT UNSIGNED DEFAULT 1 NOT NULL, "additional_headers" CLOB DEFAULT NULL)
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
INSERT INTO "sys_webhook" (uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, webhook_type, name, identifier, secret, url, method, verify_ssl, "additional_headers") SELECT uid, pid, updatedon, createdon, deleted, disabled, starttime, endtime, description, webhook_type, name, identifier, secret, url, method, verify_ssl, additional_headers FROM __temp__sys_webhook
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
DROP TABLE __temp__sys_webhook
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE INDEX parent_a82eec78 ON "sys_webhook" (pid, deleted, disabled)
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE INDEX index_source_9dce891a ON "sys_webhook" (webhook_type)
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 
CREATE UNIQUE INDEX identifier_key_75318e32 ON "sys_webhook" (identifier)
Current value: "additional_headers" CLOB DEFAULT NULL COLLATE "BINARY" 

SQLite file to reproduce attached.


Files

cms-17dbb886.sqlite (880 KB) cms-17dbb886.sqlite Garvin Hicking, 2024-07-06 08:48

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #104297: Ensure correct column type in database compare for SQLiteClosedStefan Bürk2024-07-02

Actions
Actions #1

Updated by Stefan Bürk 5 months ago

This should be already fixed with #104297 on main - can you please verify this ?

85086: [BUGFIX] Ensure correct column type in database compare for SQLite | https://review.typo3.org/c/Packages/TYPO3.CMS/+/85086

Actions #2

Updated by Stefan Bürk 5 months ago

  • Related to Bug #104297: Ensure correct column type in database compare for SQLite added
Actions #3

Updated by Garvin Hicking 5 months ago

  • Status changed from New to Closed

Of course, Stefan. I'm sorry - I didn't pay attention the patch wasn't part of the 13.2 release. Sorry. Works on 'main'.

Actions

Also available in: Atom PDF