[TYPO3-dev] typo3 4.3: mysql error caused by dam or by 4.3 trunk?

[Dmitry Dulepov]

Hi!

Uschi Renziehausen wrote:
> after upgrading my core to from 4.3 r4651 to 4.3 r4725 uploading a file
> via Media>File>Upload causes a mysql error caused by a missing table
> name in the query:
> 
> The lastBuiltQuery is:
> 
> SELECT uid_foreign
> FROM
> WHERE
> uid_local=1100
> ORDER BY sorting
> 
> and debug_backtrace says:
> 
> tx_dam_mod_file->main#248 // t3lib_SCbase->extObjContent#157 //
> tx_dam_file_upload->main#389 // tx_dam_file_upload->uploadProcessing#355
> // tx_dam_file_upload->indexUploadedFiles#544 //
> tx_dam_indexing->indexFiles#831 // tx_dam_indexing->indexFile#658 //
> tx_dam_db->insertUpdateData#845 // t3lib_TCEmain->process_datamap#348 //
> t3lib_TCEmain->dbAnalysisStoreExec#926 //
> t3lib_loadDBGroup->writeMM#6363 // t3lib_DB->exec_SELECTquery#376 //
> t3lib_DB->debug#234
> 
> This is certainly a bug, but I do not know whether it is the dam (i did
> not change anything there) or the core. Can you give me a hint under
> which category I have to place the bugreport?

I would do it in DAM first regardless of where it can be. The reason for placing it in DAM is that only DAM guys can check it (core people do not necessarily [want to] have DAM installed). Imagine if you put it into core. If someone unfamiliar with DAM (like me) decided to test it, than DAM has to be installed, learned, some other steps taken to set it up, add files, index files, etc. It takes time and not many people will want to spend time on it if there is a chance the bug is not in the core. If it is not in the core, it means that this time for the core guy will be lost. It is always a pity to loose time given the load of the core team people. On the other hand DAM guys already have all set up, they can just repeat your operation within a minute and see if the have a error. If they do, they can quickly check that tx_dam_db->insertUpdateData and other methods in the call stack. They can see if they use any MM tables and all MM fields in $TCA are defined correctly. If all i
s correct in DAM, they can forward the issue to core saying that MM handling is broken in 4.3. These are my arguments for putting it in DAM :) This is similar why I asked someone to report URL encoding issue into RealURL instead of core. I suspected that core can be the problem but I wanted to make sure that RealURL does it right first. It turned out to be a core issue (fixed by Francois in the end).

I have tt_news and irfaq that uses MM for categories. Both work ok. So I suspect that problem is not in the core.

-- 
Dmitry Dulepov
TYPO3 core team
"Sometimes they go bad. No one knows why" (Camerom, TSCC, season 1)