[TYPO3-core] RFC #13977: Improve OpenID association handling

Martin Kutschker masi-no at spam-typo3.org
Fri Apr 2 09:04:23 CEST 2010


Dmitry Dulepov schrieb:
> Hi!
> 
> This is SVN patch request.
> 
> Type: tweak (stability issue)
> 
> Branches: 4.3, 4.4
> 
> BT reference: http://bugs.typo3.org/view.php?id=13977

+1 from reading

> Q: How can character_set_* affect blob fields?
> A: Blobs do not have character sets. However connection, file system and database do have them. Therefore under certain condition ~binary~ data may become corrupted when it is sent from the application to the database. I do not have a link under hand but during my search I found that one such case caused hard to track problems with OpenID logins. After changing blob data from binary to binary safe, the problem was fixed. This is what this patch does too.

I had the same issue with serialized data in another non-TYPO3 project. I couldn't track down the
exact situation what triggers the error (not all rows were affected), but using base64 is a safe
workaround. But I admit it wasn't my idea, I found it on the Net when doing a search if others had
the same problem.

Masi


More information about the TYPO3-team-core mailing list