Project

General

Profile

Actions

Feature #22658

closed

Enable SQL Explain in BE

Added by Steffen Kamper over 14 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2010-05-16
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:

Description

In FE you have the possibility to see explained SQL if you enable the option in admPanel.

There is no such possibility in BE without hacking in source.

Introduce $TYPO3_CONF_VARS['SYS']['sqlExplainOutput'] that shows you explained SQL queries in BE.
This is absolute useful for development. Also the setting is for BE only (like sqlDebug)

(issue imported from #M14395)


Files

14395.diff (2.34 KB) 14395.diff Administrator Admin, 2010-05-16 00:53

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #22657: Better debug output for SQL ExplainClosedSteffen Kamper2010-05-16

Actions
Actions #1

Updated by Xavier Perseguers almost 13 years ago

  • Assignee deleted (Steffen Kamper)
  • Target version deleted (0)
Actions #2

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.4 (Backend)
  • Is Regression set to No
Actions #3

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #4

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #5

Updated by Mathias Schreiber about 9 years ago

  • Tracker changed from Bug to Feature
Actions #6

Updated by Riccardo De Contardi almost 9 years ago

  • Target version changed from 7 LTS to Candidate for Major Version
Actions #7

Updated by Benni Mack over 7 years ago

  • Category set to Database API (Doctrine DBAL)
Actions #8

Updated by Morton Jonuschat over 7 years ago

  • Status changed from Accepted to Rejected
  • Target version deleted (Candidate for Major Version)

In the last 24 months the database API completely changed and things like sqlDebug have gone away. This could be implemented in an external extension that hooks into the Doctrine DBAL Logging Framework and Eventhandlers, but I don't see it as a feature that few developers would use and even fewer developer actually know how to read/used. Adding this to the maintenance burden of the Core is counterproductive.

Actions

Also available in: Atom PDF