Bug #16800
closedDB file_path without a key length error after installation of DAM 1.0.8
0%
Description
After an upgrade installation of tx_dam 1.0.8 I get the following error message in the EM:
caller t3lib_DB::admin_query
ERROR BLOB/TEXT column 'file_path' used in key specification without a key length
lastBuiltQuery SELECT content
FROM cache_hash
WHERE
hash='2105c7b8901d0b5c28d922830fbf0234'
debug_backtrace sc_mod_tools_em_index->main // sc_mod_tools_em_index->showextdetails // sc_mod_tools_em_index->updatesform // sc_mod_tools_em_index->checkdbupdates // t3lib_install->performupdatequeries // t3lib_db->admin_query // t3lib_db->debug
(issue imported from #M4680)
Updated by Franz Holzinger almost 18 years ago
I have downloaded the extension in the EM.
However I did not install the downloaded one. So I get displayed now:
ALTER TABLE tx_dam ADD KEY file_path (file_path);
After this the error message has gone. Maybe this is an error with DAM then.
Updated by Joerg Schoppet almost 18 years ago
Have a look at Bug 4684. Perhaps it is a misunderstanding.
Updated by René Fritz over 17 years ago
Older versions of DAM used indexes for TEXT fields wich is not allowed. VARCHAR is now used.
BUT! See 0004684 for a general problem with indexes