Project

General

Profile

Actions

Bug #24682

closed

Queries triggered by extension installation are not displayed

Added by Francois Suter over 13 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2011-01-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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)


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #24638: Install Tool does not install extensions properlyClosedFrancois Suter2011-01-18

Actions
Related to TYPO3 Core - Epic #24849: Upgrade Wizard UsabilityClosed2011-01-31

Actions
Related to TYPO3 Core - Feature #24869: Enhance Upgrade Wizard SQL queries verbosity and error handlingClosedChristian Kuhn2011-01-28

Actions
Actions #1

Updated by Ernesto Baschny over 13 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.

Actions #2

Updated by Chris topher over 12 years ago

  • Target version changed from 4.6.0 to 4.6.1
Actions #3

Updated by Chris topher over 12 years ago

  • Target version changed from 4.6.1 to 4.6.2
Actions #4

Updated by Xavier Perseguers about 12 years ago

  • Target version deleted (4.6.2)
Actions #5

Updated by Ernesto Baschny over 10 years ago

  • Category set to Install Tool
  • Status changed from New to Closed
  • Is Regression set to No

See #24869, duplicate

Actions

Also available in: Atom PDF