[TYPO3-core] RFC: minor optimisation of getRecordRaw()
dmitry at typo3.org
Tue Dec 5 09:36:25 CET 2006
Martin Kutschker wrote:
> The function did not work out nice in the real world. The serialized
> backtrace may contain objects which in case of the FE is huge. It's so
> large that it doesn't fit in a Mysql TEXT field. I have changed the
> function so that it doesn't store the objects, but only the class names.
> Shall we use @ with all "protected" mysql_* functions? If we do this you
> must turn on logging, as no PHP warnings will popup on your dev site.
I do not think so. No idea about others but I rarely look to typo3
syslog. But I have error reporting enabled for BE (only for BE!), so I
or editors usially immediately see if there is a problem with database.
So I can go and check what happened.
> For the BE we could add something like Mozilla/Firefox's JS Console in
> IE style. Ie. when an error occurs an icon will show up. When you click
> on it you'll see log entries. But this could perhaps be done with a
> devlog extension.
I like the idea! That would really help in daily work.
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
More information about the TYPO3-team-core