You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This took me a while to track down. As it says in the comment for $_TABLES['topic_assignments'] in mysql_tableanddata.php, the max. size for the PRIMARY KEY is approaching 1000 bytes, which is a limitation in some MySQL versions.
However, that limit is actually hit during the upgrade from Geeklog 2.0.0 to 2.1.0:
from sql/updates/mysql_2.0.0_to_2.1.0.php, lines 25+26
So you end up with len(tid + id + type) = 286, which is 1144 bytes for the utf8mb4 collation.
Simply commenting out / removing line 25 (for the tid) in mysql_2.0.0_to_2.1.0.php fixes the problem for me, but I'm not sure if that's the best approach.
The text was updated successfully, but these errors were encountered:
dhaun
added
the
Bug
An issue describing unexpected or malicious behaviour.
label
May 14, 2023
This took me a while to track down. As it says in the comment for
$_TABLES['topic_assignments']
in mysql_tableanddata.php, the max. size for the PRIMARY KEY is approaching 1000 bytes, which is a limitation in some MySQL versions.However, that limit is actually hit during the upgrade from Geeklog 2.0.0 to 2.1.0:
from sql/updates/mysql_2.0.0_to_2.1.0.php, lines 25+26
So you end up with len(tid + id + type) = 286, which is 1144 bytes for the utf8mb4 collation.
Simply commenting out / removing line 25 (for the tid) in mysql_2.0.0_to_2.1.0.php fixes the problem for me, but I'm not sure if that's the best approach.
The text was updated successfully, but these errors were encountered: