[TYPO3-core] RFC: devLog in t3lib_db

Dmitry Dulepov dmitry at typo3.org
Fri Dec 1 12:44:13 CET 2006


This is SVN patch request

Branches: hope for both ;) (4_0 after 4.0.3!)

Problem: if invalid recordset is passed to t3lib_db::sql_* functions, it 
may/will output PHP error message without any real information for 
solving the problem.

Solution: add a simple check for recordset validity and report stack 
trace to devLog if recordset is not valid. This allows to quickly 
discover database problems (crashed tables, non-updated tables, etc) 
even on a live site without visitors noticing anything.

This was discussed a little in the thread named "RFC: minor optimization 
of getRecordRaw()" and I made a simple patch.

What do you think?

Dmitry Dulepov

Web: http://typo3bloke.net/
Skype: callto:liels_bugs

"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: t3lib_db_devLog.txt
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20061201/6d4c7634/attachment.txt 

More information about the TYPO3-team-core mailing list