[TYPO3-core] RFC: #0012381: Bug: Change definition of DB table fields

Ries van Twisk typo3 at rvt.dds.nl
Wed Oct 28 16:51:09 CET 2009


On Oct 28, 2009, at 10:40 AM, Xavier Perseguers wrote:

> Hi Francois,
>
>>> Problem:
>>> The fields "serialized_task_object" & "serialized_executions" are  
>>> defined as "TEXT" this can be a problem with charset convertion  
>>> from database to your system.
>>>
>>> Solution:
>>> It is a good practise to define such serialized fields as "BLOB"  
>>> because this is a binary field where no charset convertions are  
>>> made on.
>>>
>>> So just, change the fields from "TEXT" to "BLOB".
>> There's has been a move in recent years to use TEXT fields  
>> throughout the TYPO3 core rather than BLOBs. If you look at all the  
>> cache tables, they use TEXT fields. So I would rather tend to leave  
>> the fields as is.
>> What do others think?
>
> I think that I found recently some very strange characters in a  
> scheduler task serialized string in a MySQL database and I'd say  
> that this serialized array is already as of today transformed on the  
> way to the DB with character set conversion. Even if it seems to  
> work because it is being reconverted the way back to TYPO3, I don't  
> like it.
>
> Thus +1 for this change.
>



side note: I have seen some other Open Source tools using base64  
encoding/decoding to avoid all problems al together.

Ries




More information about the TYPO3-team-core mailing list