Bug #4046
closed
Do not use blob fields in the event table
Added by Ingo Renner over 15 years ago.
Updated almost 11 years ago.
Description
Instead of using blob fields it should be good enough to use simple text fields. Thus you can quickly see wahts going on in case you have to look at it through phpMyAdmin f.e. - for whatever reason...
I know that text fields are preferred. I was just wondering if it were appropriate here too, since those fields contain serialized objects. I agree that text fields are more easily visible in phpMyAdmin, but they could also be edited, which is a dangerous operation. What do you think?
- Status changed from New to Accepted
- Assignee set to Ingo Renner
Francois Suter wrote:
I know that text fields are preferred. I was just wondering if it were appropriate here too, since those fields contain serialized objects. I agree that text fields are more easily visible in phpMyAdmin, but they could also be edited, which is a dangerous operation. What do you think?
yes, in the first place I wanted to have a look "into" these fields. Whoever edits these fields should know what he's doing anyway...
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1027.
Ingo Renner wrote:
Whoever edits these fields should know what he's doing anyway...
Sure. Fine with the change.
- Status changed from Resolved to Closed
- Category set to scheduler
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by