Bug #20400
closed
DBAL does not support CLOB/BLOB when using a mapped table name
0%
Description
When dealing with CLOB/BLOB fields, special care should be taken in INSERT and UPDATE statements. However DBAL does not handle it carefully when the query contains a mapped table name, e.g., when using this configuration:
$TYPO3_CONF_VARS['EXTCONF']['dbal']['mapping'] = array(
'tx_templavoila_datastructure' => array(
'mapTableName' => 'tx_templavoila_ds',
),
);
In this case, the query contains table 'tx_templavoila_ds' instead of 'tx_templavoila_datastructure' and DBAL is not able anymore to detect that a column is of type BLOB/CBLOB leading to an invalid query being issued to the database.
(issue imported from #M11047)
Files
Updated by Xavier Perseguers over 15 years ago
Same problem arises when mapping fields actually:
$TYPO3_CONF_VARS['EXTCONF']['dbal']['mapping'] = array(
'tx_templavoila_datastructure' => array(
'mapTableName' => 'tx_templavoila_ds',
'mapFieldNames' => array(
'dataprot' => 'my_dataprot',
),
),
);
v2 fixes this too.
Updated by