[TYPO3-dam] brand new typo3 installation & DAM: only error messages PROBLEM SOLVED

[grac]

hi everybody

problem solved - table tx_dam created!

it was in the end not complicated.
the problem was to find the right hints:


1. a thread in the forum

"TYPO3.net - DAM Tabelle tx_dam läßt sich nicht installieren"
(title: table tx_dam cannot be created), to find under

http://www.typo3.net/forum/list/list_post//84965/?page=1&sword=dam#pid317649

from 12.12.2008, which included the same additional compare-statement i 
had and didn't seem related to dam:

Add fields
ALTER TABLE sys_refindex ADD KEY lookup_string (ref_table,ref_string(400));

Add tables CREATE TABLE tx_dam (
uid int(11) NOT NULL auto_increment,
pid int(11) NOT NULL default '0',
tstamp int(11) unsigned NOT NULL default '0',
...


2. a response in this thread which referred to a link about the problem 
with sys_refindex:

"sys_refindex ref_string(400)-Problem"

http://typo3.sfroemken.de/index.php?id=4&tx_ttnews
[tt_news]=19&tx_ttnews[year]=2009&tx_ttnews
[month]=01&tx_ttnews[day]=29&cHash=ebd94d2b9f

this link leaded to ...


3. a blog-entry from stefan frömken, dated 29.01.2009

which dealt with the correct utf-8 implementation in a new typo3 
installation.
under others it says that the variable "multiplyDBfieldSize" should have 
the value of = 1


4. a check in my all-configuration showed that i had 
"multiplyDBfieldSize = 2" (no idea where it came from - maybe from the 
EXT db_ttv).
this entry leaded the author to sys_refindex/ref_string(400) as 
described under 1.


4. after deleting the value = 2 the comparison finally allowed to create 
the table tx_dam and all the necessary fields.
(and all the other necessary fields in other tables.)


5. a second round finally allowed to change the

ALTER TABLE sys_refindex ADD KEY lookup_string...



so finally dam is now to be used.
and there are no MySQL error messages or warnings any more.



i wrote this in full length for others who have the same problem as i had.

so it was not dam nor MySQL, but an incorrect value of a totally 
different variable!
maybe a hint in the dam-documentation could help?!


@georg

> PS: FULL-ACK to 5.1-RC in production-envs; upgrading to rc-versions with 
> the excuse of "security" seems pretty stupid to me;

please tell this my webhoster.
i'm sure he has an answer for you.


stephan