#109295Deprecate DatabaseWriter::setLogTable() / getLogTable()
Description
TYPO3\CMS\Core\Log\Writer\DatabaseWriter has setLogTable()/@getLogTable()@ methods allowing users to redirect log output to a custom database table.
This API creates a false sense of flexibility: DatabaseWriter hard-codes field names (request_id, time_micro, component, level, message, data) that are specific to sys_log, so any custom table must replicate the full sys_log schema to work correctly.
This also hinders TYPO3 to make meaningful changes to DatabaseWriter, because that would easily be breaking for users with custom tables.
Proposed change:
- Deprecate
setLogTable()andgetLogTable()inDatabaseWriterwith adeprecated@ annotation and atrigger_error('...', E_USER_DEPRECATED)call. - Add a changelog .rst deprecation note.
- Plan to make DatabaseWriter final and remove $logTable entirely in a future major version.
Migration path for affected users:
If you are using setLogTable() to write to a custom table, implement a dedicated writer by subclassing AbstractWriter and implementing writeLog() with explicit field mapping for your table’s schema. This is also more future-proof since your mapping won’t break when sys_log evolves.
Example:
class MyCustomTableWriter extends AbstractWriter
{
public function writeLog(LogRecord $record): WriterInterface
{
GeneralUtility::makeInstance(ConnectionPool::class)
->getConnectionForTable('my_log_table')
->insert('my_log_table', [
'created' => (int)$record->getCreated(),
'level' => $record->getLevel(),
'message' => $record->getMessage(),
]);
return $this;
}
}
// Before:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['writerConfiguration'][\Psr\Log\LogLevel::WARNING] = [
\TYPO3\CMS\Core\Log\Writer\DatabaseWriter::class => ['logTable' => 'my_custom_log'],
];
// After:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['writerConfiguration'][\Psr\Log\LogLevel::WARNING] = [
\MyVendor\MyExtension\Log\Writer\MyCustomTableWriter::class => [],
];Reviews 2
Related issues 1
History 39
-
Gerrit Code Review pushed patch set 1 for main to change 93283 status
NewUnder Review <span data-processor="relativetime" data-value="2026-03-19T20:53:25+00:00" > 03/19/26, 20:53 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93283 <span data-processor="relativetime" data-value="2026-03-19T20:54:16+00:00" > 03/19/26, 20:54 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 93283 <span data-processor="relativetime" data-value="2026-03-20T05:48:15+00:00" > 03/20/26, 05:48 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 93283 <span data-processor="relativetime" data-value="2026-03-20T08:15:10+00:00" > 03/20/26, 08:15 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 93283 <span data-processor="relativetime" data-value="2026-03-20T08:16:58+00:00" > 03/20/26, 08:16 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 93283 <span data-processor="relativetime" data-value="2026-03-20T10:02:15+00:00" > 03/20/26, 10:02 </span>
-
Sebastian Michaelsen commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-03-21T20:50:09+00:00" > 03/21/26, 20:50 </span> -
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:09:46+00:00" > 03/31/26, 08:09 </span> -
Christian Kuhn changed Related to #109952 <span data-processor="relativetime" data-value="2026-06-01T23:13:14+00:00" > 06/01/26, 23:13 </span>
Applied in changeset commit:393e8cb7e55a8bd2ef37b912ceab999b2fd79e79.