[TYPO3-core] RFC #11047: DBAL does not support CLOB/BLOB when using a mapped table name
Xavier Perseguers
typo3 at perseguers.ch
Thu May 7 17:46:43 CEST 2009
Hi,
> This is a SVN patch request.
>
> Type: Bugfix
>
> Branches: trunk (other branches might apply too)
>
> BT reference: http://bugs.typo3.org/view.php?id=11047
>
> Problem:
> 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.
>
> Solution:
> Make sure the original table name is used when retrieving a field's
> metatype.
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 (for completeness).
--
Xavier Perseguers
http://xavier.perseguers.ch/en
One contribution a day keeps the fork away
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 11047_v2.diff
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090507/fa0f1d82/attachment.txt
More information about the TYPO3-team-core
mailing list