Bug #24682
closedQueries triggered by extension installation are not displayed
0%
Description
In every update wizard it is possible to check a box labeled "Show database queries performed". The patch discussed here makes it possible to trigger a clean installation of an extension, including the relevant database changes (see 0017114). However the queries that may be triggered by this installation process are not displayed when the box is checked. It's a rather minor issue, although still somewhat disturbing for admins: it's not really nice to have tables created silently when you thought you had requested the tool to be verbose about queries being executed.
(issue imported from #M17166)
Updated by Ernesto Baschny almost 14 years ago
Good catch. The "sql logging" is done manually by each upgrade wizard, so its not tracking the SQL executions on the source.
e.g:
$res = $GLOBALS['TYPO3_DB']->exec_UPDATEquery('pages', 'doktype=2', $updateArray);
$dbQueries[] = str_replace(chr(10), ' ', $GLOBALS['TYPO3_DB']->debug_lastBuiltQuery);
...
Since the SQL creation through the EM happens in "some nested down" methods, it is not so easy to get to that information.
Best solution would be to add a method on t3lib_db to "startTrackingQueries" (only INSERT/DELETE/REPLACE) and "stopTrackingQueries" where the wizard caller can later simply call "fetchTrackedQueries" or something like this. Then we would get all queries that modified something (which went through t3lib_db at least). But this also has to consider DBAL etc.. Probably something interesting for 4.6.
Updated by Chris topher about 13 years ago
- Target version changed from 4.6.0 to 4.6.1
Updated by Chris topher almost 13 years ago
- Target version changed from 4.6.1 to 4.6.2
Updated by Ernesto Baschny about 11 years ago
- Category set to Install Tool
- Status changed from New to Closed
- Is Regression set to No
See #24869, duplicate