Bug #80318
closeddbal rename mapFieldNames doesn't work for more than one record/row
0%
Description
The rename of the return array doesn't work correctly.
If you get more then on record/row from the external database, only the first record keys (from the return array) will renamed.
So you can't handle the other records/row, especially if u map uid.
It will resu
Setup:
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['dbal']['handlerCfg'] = array( '_DEFAULT' => array( 'type' => 'native', 'config' => array( 'username' => '', 'password' => '', 'host' => '', 'database' => '' ) ), 'external_db' => array( 'type' => 'native', 'config' => array( 'username' => 'external_db_user', 'password' => 'external_db_pass', 'host' => 'external_db_host', 'database' => 'external_db_database', ) ), ); $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['dbal']['table2handlerKeys'] = array( 'external_db_table' => 'external_db', ); $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['dbal']['mapping'] = array( 'local_db_table' => array( 'mapTableName' => 'external_db_table', 'mapFieldNames' => array( 'local_db_table_column' => 'external_db_table_column' ) ) );
Updated by Riccardo De Contardi over 6 years ago
- Status changed from New to Closed
I feel really sorry for this so late update; I close this issue for now: EXT:dbal is considered obsolete on 8.7.x and, albeit version 7 is still in high priority bugfix mode, a fix for version 7 can not be planned as fixing dbal is not a priority.
I'm opening this issue under https://github.com/FriendsOfTYPO3/dbal (https://github.com/FriendsOfTYPO3/dbal/issues/8) feel free to continue there and accept our apologies.
If you think that this is the wrong decision, please reopen this issue or open a new issue with a reference to this one. Thank you.