Issue Bug Rejected

#104155inconsistence of database definition for field sys_refindex.ref_uid (possible overflow)

Bernd Wilke 06/19/24, 14:05 updated 06/20/24, 10:16

Description

is this a possible point of failuer in TYPO3 core?
while having another failure thrown with lolli/dbdoctor (https://typo3.slack.com/archives/C025BQLFA/p1718718362856409) I think I found an inconsistence in core database definitions:
It’s about definitions and usage of `sys_refindex.ref_uid while I understand that uids (unsigned int) are stored I also found some records with negative numbers for tables fe_users and sys_languages`, which might be valid as the negative values are used for ‘any language’, ‘any login’, ‘no login’

as the field sys_refindex.ref_uid is defines as (signed) int it might fail if there is stored an uid from the upper half range of unsigned int (> 2147483647 )

is it intended that negative numbers are stored? (as the field is defined as type int) => what will happen if a uid like 3147483647 has to be stored?

a possible solution might be to use `bigint` for this field (or a special handling if big uids occur)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.