Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

type="object" functionality broken #639

dompie opened this Issue Mar 27, 2013 · 4 comments


None yet
4 participants

dompie commented Mar 27, 2013


I have encountered a problem when trying to store type="object" objects into PostgreSQL 9.1 Database with PHP 5.3.xx together with another user. See Google group discussion here:

When creating a column type="object" in propel schema.xml the corresonding DB column type is created as type "text" (on PostgreSQL 9.1 DB). This breaks with serialize() specification as serialize may also return null byte (\0) characters for private properties.
Somehow this seems to break PDO, so incomplete serialization strings are stored to database making it impossible to unserialize them.

Don't know if this also affects MySQL and other DBs.

dompie commented Mar 27, 2013

I have seen this behavior in Propel '1.7.0-dev' and '1.6.9' with PHP 5.3.10 + PostgreSQL 9.1.9. Did not test on MySQL.


willdurand commented Apr 11, 2013

Ok, thanks for reporting the issue.

Bonscho commented Dec 17, 2014

Is there any solution for this problem?
Using Propel 1.7.0 with PHP 5.5.9 and PostgreSQL 9.3.


marcj commented Dec 18, 2014

This is fixed in 2.0.

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