t3lib_DB debug_check_recordset for exec_SELECT_*
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.
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.