Bug #15915
closedDatabase Analyser does not create sys_refindex if multiplyDBfieldSize is set
0%
Description
Using the "Compare"-function from the Database Analyser fails to create the table "sys_refindex" with the following error message if $TYPO3_CONF_VARS[SYS][multiplyDBfieldSize]=2 is used (the database analyser than tries to create a field of type TEXT instead of VARCHAR):
BLOB/TEXT column 'ref_string' used in key specification without a key length
To solve this a length has to be assigned to the key referencing the column "ref_string".
This happens because MySQL needs to know how many bytes of a BLOB column should be indexed. See [1] for an explanation.
The MySQL version used on the server- or client-side is not relevant here.
This error is likely to happen in other extensions as well when index is used on BLOB columns.
[1]<http://groups.google.com/group/mailing.database.myodbc/msg/2055be92b8d210e4>
(issue imported from #M3015)
Files
Updated by Andreas Otto † over 18 years ago
No, 0002511 does not change anything related to keys.
Updated by Ingmar Schlecht over 18 years ago
This one is indeed fixed in TYPO3-4.0rc2 by bugfix to #15772.
Read the related thread from the team-core mailinglist:
http://lists.netfielders.de/pipermail/typo3-team-core/2006-March/003641.html
cheers,
ingmar
Updated by Andreas Otto † over 18 years ago
Please see http://lists.netfielders.de/pipermail/typo3-team-core/2006-March/003720.html to find out that this issue is not a duplicate and thus not resolved.
Updated by Ingmar Schlecht over 18 years ago
If I get it right, the problem only occurs when multiplyDBfieldSize is set.
This setting is no longer needed, according to a post by Karsten Dambekalns:
http://lists.netfielders.de/pipermail/typo3-team-core/2006-March/003739.html
Thus I marked this issue as won't fix. Please re-open the bug if it does not work for you.
cheers,
Ingmar