Actions
Feature #22723
closed
hundreds of SQL debugs are unusable
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2010-05-26
Due date:
% Done:
0%
Estimated time:
PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:
Description
When I turn SQL debug output on, then I get too many SQL debug windows. This is unusable.
Nobody will be able to find the SQL statement he is interested in.
Why can't everything be shown in only one window where you can search?
(issue imported from #M14487)
Files
Updated by Alexander Opitz about 11 years ago
- Tracker changed from Bug to Feature
- Target version deleted (
0)
There was a little discussion on the TYPO3 Code Sprint in Hannover about this issue. Will mark this as feature.
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7 LTS
We'll see what the new debug windows could do.
Updated by Benni Mack about 9 years ago
- Target version changed from 7 LTS to 8 LTS
Updated by Riccardo De Contardi about 8 years ago
- Category set to Backend User Interface
- Status changed from New to Accepted
- Target version deleted (
8 LTS)
Updated by Benni Mack over 7 years ago
- Status changed from Accepted to Needs Feedback
Can you tell me if doctrine DBAL helps us here in any way as we implemented it in v8?
Updated by Franz Holzinger over 7 years ago
I cannot answer now, because I must first move the extension debug_mysql_db from $GLOBALS['TYPO3_DB'] to TYPO3 8 and the support of DOCTRINE.
Updated by Christian Kuhn almost 7 years ago
- Status changed from Needs Feedback to Closed
closing this issue since sqlDebug has been droppend entirely, meanwhile.
Actions