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

[Peter Kuehn [wmdb>]]

hi grac, hi yall,

 > at least the error message in the module "info" was clear:
 > Table '....tx_dam' doesn't exist

@DAMsters: does someone of you have a MySQL 5.1 install available for 
testing? sounds like the definition for tx_dam in ext_tables.sql does 
not create the table on that version - if so, this imho will become a task.
I could build a testing env but it would take some time...

 > MySQL version: 5.1.29-rc
@grac: thnx for the hint - but the code is meant to work in production. 
sometimes it might become to hard to handle things to come like rc´s.

grac schrieb:
> hello again
> 
> after a total crash with a former version of dam and after having waited 
> for the next stable version of dam 1.1.1 i tried to install it again - 
> this time in a brand new installation and clean of typo3 4.2.5 with 
> templavoila and YAML (EXT dbttv).
> 
> nothing else.
> 
> everything went absolutely smooth - until i tried dam.
> 
> nothing but error messages:
> 
> about 20 times in the module "datei" (file):
> Warning: mysql_num_rows(): supplied argument is not a valid MySQL result 
> resource in /.../t3lib/class.t3lib_db.php on line 796
> 
> three times in module "liste "(list):
> Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL 
> result resource in /.../t3lib/class.t3lib_db.php on line 809
> 
> at least the error message in the module "info" was clear:
> Table '....tx_dam' doesn't exist
> 
> and the module "tools" again with two error messages:
> 
> Warning: reset() [function.reset.php]: Passed variable is not an array 
> or object in 
> /.../typo3conf/ext/dam/modfunc_tools_indexupdate/class.tx_dam_tools_indexupdate.php 
> on line 304
> 
> 
> so i checked in the install tool/database analyser.
> and right, there was a whole table which was not generated.
> and fields in other tables that were not created as well.
> 
> and could not be generated.
> whatever i tried.
> 
> MySQL version: 5.1.29-rc
> 
> 
> so: who is to blame? the EXT or MySQL? or both?
> 
> 
> thanks for any hints and help
> 
> stephan