Commit 10a4e286 authored by Christian Kuhn's avatar Christian Kuhn
Browse files

[BUGFIX] Fix sqlite bigint from ext_tables.sql issue

Table sys_messenger_messages introduced with #97700
declares a bigint(20) as primary key in ext_tables.sql.

ext_tables.sql is essentially mysql syntax, the core
SchemaMigrator creates a doctrine object structure
from it, and struggles with bigint on sqlite, found
by a nightly test.

A simple fix is to declare a "casual" int(11), which
should be more than big enough for this table and
is in line with our other "uid" column primary keys
of other tables.

Resolves: #99689
Related: #97700
Releases: main
Change-Id: I5322aefe0f8e9b93015eaf2fb7af1ae8536b94ae

Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <>
Tested-by: core-ci's avatarcore-ci <>
Reviewed-by: Susanne Moog's avatarSusanne Moog <>
Tested-by: Christian Kuhn's avatarChristian Kuhn <>
Tested-by: Anja Leichsenring's avatarAnja Leichsenring <>
Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
Tested-by: Stefan Bürk's avatarStefan Bürk <>
Reviewed-by: Stefan Bürk's avatarStefan Bürk <>
Reviewed-by: Georg Ringer's avatarGeorg Ringer <>
parent ca78178c
......@@ -397,7 +397,7 @@ CREATE TABLE sys_category (
# Table structure for table 'sys_messenger_messages'
CREATE TABLE `sys_messenger_messages` (
id int(11) unsigned NOT NULL auto_increment,
body longtext NOT NULL,
headers longtext NOT NULL,
queue_name varchar(190) NOT NULL,
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment