Project

General

Profile

Actions
Copy link

Bug #14513

closed

general problems with fulltext keys in tables (extension manager failures)

Added by old_jmziem almost 20 years ago. Updated over 18 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Karsten Dambekalns
Category:
-
Target version:
-
Start date:
2005-01-27
Due date:
% Done:

0%

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

Description

if you use dbal(or even the old t3 system) the mapping of keys generate within
typo3\em\index.php funtion checkDBupdates()
>linked within install>getDatabaseExtra(...)
is simply wrong. the sql wrapper classes (class.db*, class.sql_*) only knows primary keys, [unique] keys and nothing else.

so if you add a fulltext key within your table, this extension manager ALWAYS want's to update the table, and it produces ALWAYS a table error - of course.

create an extension, and add within the ext_tables.sql within the table a fulltext index over a text field. this ALWAYS reproduced that error.

the problem itself came (i think) from field $diff:
em->index.php line 3576 (function checkDBupdates) where the getDatabaseExtra() stores the fulltext key as "unknown" and so as "FIELD" instead of key mark.
so the diff always failed.

i didn't understand the confusing system within the sql wrapper which tests and extracts all keys... so i couldn't fix it alone.
(issue imported from #M718)

Actions
Copy link

Also available in: Atom PDF