JSON vs. Serialized Array in database [closed]

Answer 1

Use json for for arrays and communication with Javascript or other language. Use serialize for object or any internal PHP work for the current running script.

Answer 2

1. JSON encode() & decode()
   • PHP Version >= 5.0.0
     • Nesting Limit of 20.
   • PHP Version >= 5.2.3
     • Nesting Limit of 128.
   • PHP Version >= 5.3.0
     • Nesting Limit of 512.
   • Small footprint vs PHP's serialize'd string.
2. serialize() & unserialize()
   • PHP Version >= 4.0.0
     • Methods are not lost on PHP Datatype Object.
     • __wakeup() magic method called on any object being unserialize. (VERY POWERFUL)
     • It has been noted that it is some times best the base64 encode strings put into the database, and base64 decode strings taken out of the database with this function, as there are some issues with the handling of some white space characters.

The choice is yours.

Answer 3

JSON is more portable, i.e. you can more easily read/write to it from different languages etc. If you used PHP serialized arrays you would only be able to easily use PHP to access it.

Answer 4

I just had this big problem with php serialize. I stored a lot of data in a single field in which i used unserialize to read.

What happened is that I got some corrupt data in that field. Serialize map the data with codes like 'a','s' and 'N'. If there is corrupt data, the map failed. It will show a php error that the unserialize function is unable to work because of byte code error.

So my point is to avoid serialize. Go with JSON, way safer and you won't bang your head on future majors problems.

For me, no more serialize.

Answer 5

Portability: Winner JSON. JSON is supported on a wider variety of platforms, while PHP de-serialization is only supported (as far as I know) by PHP. While it's possible to parse either format in any language, JSON has more pre-built libraries.

Future Proof: Winner JSON. JSON is a "standard", in the sense that Javascript is a standard, and isn't likely to change anytime in the future. The PHP group has made no promises about the future of the serialization format, and while it's unlikely to change in the future, the fact that a single group controls the format means you may end up with future data that's unreadable.

Fidelity: Winner PHP. PHP serialization will allow you to store data with native PHP data types, including objects defined by custom classes. JSON will only allow you to store generic primitive types, lists of primitive types ("arrays") and key/value pair Objects. PHP Serialization may provide some advantages here if you're developing a PHP application.

File Size: JSON has a slight win here, as PHP's current serialization format is more verbose (as it's storing more information).

Performance: Who knows, it depends, profile.

Conclusion: Go with JSON unless you have a compelling reason to use PHP Serialization .