[DBAL-369] [GH-219] Fix storage of binary data for array and object types Created: 19/Oct/12  Updated: 20/Dec/13  Resolved: 20/Dec/13

Status: Resolved
Project: Doctrine DBAL
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Bug Priority: Major
Reporter: Benjamin Eberlei Assignee: Benjamin Eberlei
Resolution: Invalid Votes: 0
Labels: None


 Description   

This issue is created automatically through a Github pull request on behalf of kdambekalns:

Url: https://github.com/doctrine/dbal/pull/219

Message:

serialize() returns binary data (NUL bytes) and not all platforms
handle that in CLOB fields (e.g. PostgreSQL).

This change uses base64 encoding to work around that, and transparently
reads (old) non-base64 data as well.

Fixes DBAL-368



 Comments   
Comment by Karsten Dambekalns [ 05/Aug/13 ]

Any comments on that? Any chance this will go into DBAL at some point?

Comment by Benjamin Eberlei [ 05/Aug/13 ]

Karsten Dambekalns Would it make sense instead to use a BLOB instead of a CLOB and have a flag in AbstractPlatform called "supportsNullByteInClob()"? This would not be BC, but i would prefer this way. We would need BC by adding this in a new PostgreSQL platform or sometihng like that

Comment by Doctrine Bot [ 03/Dec/13 ]

A related Github Pull-Request [GH-219] was closed:
https://github.com/doctrine/common/pull/219

Comment by Doctrine Bot [ 20/Dec/13 ]

A related Github Pull-Request [GH-219] was closed:
https://github.com/doctrine/dbal/pull/219

Generated at Thu Apr 17 09:49:55 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.