TYPO3 Core

My installation was created from scratch with DBAL, following the instructions at http://typo3.org/documentation/document-library/extension-manuals/dbal/current/view/1/4/

The DBAL specific part of typo3conf/localconf.php is included as additional information.

The problem arises when installing extensions which require database changes. More often than not, the installer creates extension tables in the "arpac" database instead of using "_DEFAULT".

When looking at the installed and running extension, it always requests an update to the database (likely because it can't find the table in the _DEFAULT database) but when the update is executed, it's on the wrong database, leaving me at square one.

It is not neccesarely every time, as about 50% of my installed extensions have their tables in "_DEFAULT" and the rest in "arpac".

Any other information required or is this a feature of some sort?

$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array (
'_DEFAULT' => array (
'type' => 'adodb',
'config' => array(
'driver' => 'mysql',
)
),
'arpac' => array (
'type' => 'adodb',
'config' => array(
'username' => '***',
'password' => '***',
'host' => 'localhost',
'database' => 'Arpac_dbo_test',
'driver' => 'mysql',
)
),
);

$TYPO3_CONF_VARS['EXTCONF']['dbal']['table2handlerKeys'] = array (
'Candidate' => 'arpac',
'CountryCode' => 'arpac',
);

$TYPO3_CONF_VARS['EXTCONF']['dbal']['debugOptions'] = array(
'enabled' => true, // Generally, enable debugging.
'printErrors' => FALSE, // Enable output of SQL errors after query ex
ecutions.
'EXPLAIN' => 1, // EXPLAIN SELECT ...(Only on default handler)
'parseQuery' => 1, // Parsing queries, testing parsability (All q
ueries)
'joinTables' => 1
);
(issue imported from #M3638)