Task #32269: t3lib_DB debug_check_recordset for exec_SELECT_* - Logging Project - TYPO3 Forge

CMS-Garden Composer Team Editorial Team Extension Comparison Extension Coordination Team Marketing Team Sandbox Screencast Team Server Team Translation Team (archived projects)BLE Project DEV3 flow3.typo3.org Logging Project ReStructured Text Infrastructure TYPO3 Flow TYPO3 Neos

Task #32269

t3lib_DB debug_check_recordset for exec_SELECT_*

Added by Alexander Wahl over 10 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Steffen Müller

Category:

Integration

Start date:

2011-12-02

Due date:

% Done:

Estimated time:

TYPO3 Version:

6.2

Description

Syslog-Entries and or devlog-entries are written in function debug_check_recordset.

Altough functionality is already implemented, debug_check_recordset is not called from exec_SELECT-Querys because debug_check_recordset is called AFTER (!$this->sql_error()). So it never get's called.

So any error that occurs, will not be traced within debug_check_recordset. So this function at this point is usless.

Maybe providing a syslog entry within sql_error() would be a better approach because all sql-errors are then tracked within the syslog or errorlog.

Greetings
Alexander

Updated by Michael Stucki over 10 years ago

Status changed from New to Needs Feedback

Hmm, we could easily replace the sql_error() call with the same debug_check_recordset() method. IMHO this should have the same effect, what do you think?

Updated by Alexander Wahl over 10 years ago

yes. That whould be great. But in my opinion, besides the SQL-Error message the last query stored in debug_lastBuiltQuery should also be logged into devlog/syslog. This would save a lot of time.

Therefore storeLastBuiltQuery must be initially true.

At the moment, when an SQL-Error occurs in Extension, you have to edit the Extension to output the last SQL-Query to see where the problem is or developer has implemented his own error-catching mechanism.

So my feature request would be a more global approach to error logging. If something goes wrong, you only have to activate DEVLOG or SYSLOG and search the entries to find the bug.