The DBAL is configurable through
. This table is an
overview of the main keys in this array:
handlerCfg[ handlerKey ] ¶
handlerCfg[ handlerKey ]
Configuration of each data handler you want to use in the system.
Each handler is identified with a string (
) which is used in
configuration (see below) to pair table names
a default handler needed which has the handlerKey
“_DEFAULT”. By default this handler is configured with the classic
username/password/host and database settings from
If you want to use ADOdb or just need to store a table in another
database you can configure a handler here and map the tables you need
to that handler (with
, see below).
table2handlerKeys[ tablename ] ¶
table2handlerKeys[ tablename ]
Using other handlers than the “_DEFAULT” handler key is possible on a per-table basis and simply done by entering the table name as key in this array and letting the value be the handlerKey you want to use for this table!
The table names here are the values of
not the names that TYPO3 will use; thus the real table names.
Notice: If tables are joined both tables must use the same handlerKey. If they do not TYPO3 will exit with a fatal error!
You can use the debug options to track all table joins and assess which tables can safely be handled together.
mapping[ tablename ] ¶
mapping[ tablename ]
Configuration of mapping of table and fieldnames. For instance you can
configure that TYPO3 should use a physical table in the database named
. Or you can map fieldname in a
The point is that TYPO3 always sees a table or field names as TYPO3 requires internally but in reality the table- or field name could be something different in the physical database source.
There is a performance loss by configuring such mapping of course: Result rows are preprocessed before being returned and all SQL queries are parsed, transformed and re-compiled again before execution.