Use BLOB for Object mapping type #273

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
5 participants

http://php.net/manual/en/function.serialize.php

Note that this is a binary string which may include null bytes, and needs to be stored and handled as such. For example, serialize() output should generally be stored in a BLOB field in a database, rather than a CHAR or TEXT field.

@ludekstepan ludekstepan Use BLOB for Object mapping type
http://php.net/manual/en/function.serialize.php
Note that this is a binary string which may include null bytes, and needs to be stored and handled as such. For example, serialize() output should generally be stored in a BLOB field in a database, rather than a CHAR or TEXT field.
72b7142

Hello,

thank you for positing this Pull Request. I have automatically opened an issue on our Jira Bug Tracker for you with the details of this Pull-Request. See the Link:

http://doctrine-project.org/jira/browse/DBAL-448

Oh btw, I just (automatically) realized that you are not creating this pull request against the master branch.

Unless there are good reasons for this, i would suggest to close and rebase the Pull Request against master and then create it again. Sorry!

ludekstepan referenced this pull request in schmittjoh/JMSJobQueueBundle Feb 17, 2013

Closed

Use DBAL object serialization mechanism #19

Owner

beberlei commented Mar 12, 2013

This is a BC break, we can't do it this way. You need to introduce a new type.

beberlei closed this Mar 12, 2013

schmittjoh referenced this pull request in schmittjoh/JMSJobQueueBundle Jun 23, 2013

Closed

IMPORTANT: stackTrave is not saving correctly and breaks the queue #29

Member

schmittjoh commented Jun 23, 2013

How about introducing a new type in DBAL, something like safe_object?

Why not do it like in #219 - that is backwards compatible.

The whole serialized -> CLOB idea is just broken on PostgreSQL. Always was. I wonder why so little people seem to notice.

Owner

beberlei commented Aug 5, 2013

@kdambekalns I suppose if you run in the trouble you can just write your own type and be done with that. Also I suppose not many people use the object and array types, because they are sort of hackish. I posted a possible solution to the jira ticket.

I don't want to burden every platform with base64 encoding for these types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment