ID: 46882
User updated by: max at phoenixweb dot it
Reported By: max at phoenixweb dot it
Status: Open
Bug Type: Variables related
Operating System: Centos 5.2 x86 64bit
PHP Version: 5.2.8
New Comment:
But this is a problem.
Serialize is needed to store PHP object as a string. Is this correct?
There are a lot of possibility of needed an object as a string, like
complex data storage, and pass data from a server to another server.
If the data is not unserializable from a different server, it's
completely useless.
When i'll upgrade my server to 12Gb of RAM (needing a 64bit OS), i'll
have to trash all the data stored with SERIALIZE on my MySqls?
I don't think that the correct way is just to add a comment to the
current documentation.
I think this should be consider a bug, cause SERIALIZE / UNSERIALIZE is
used to storage data and pass it across servers, so must be compliant
with the problems of differents OS system behaviours.
Previous Comments:
------------------------------------------------------------------------
[2008-12-16 15:13:54] crrodriguez at opensuse dot org
This behavior is expected, but the documentation of serialize() does
not mention it, this is a documentation problem.
------------------------------------------------------------------------
[2008-12-16 15:03:19] max at phoenixweb dot it
As I can see from the Function Manual, JSON is not a possible
alternative due to his limitation in nested elements.
So... i have to wait that somebody fix this one.
:(
------------------------------------------------------------------------
[2008-12-16 14:54:16] max at phoenixweb dot it
Description:
------------
The problem is easy.
I use SERIALIZE - UNSERIALIZE to pass complex PHP objects between
server e store it on remote.
However the SERIALIZE - UNSERIALIZE process fail while this happens
between a 64bit OS and a 32bit OS, due to a missbehaviour in the number
rappresentation (int).
For the 64bit the (INT) is the correct data type for the number:
4139868160 while for a 32bit system that numbero can handled only by a
(DOUBLE)
s:3:"mem";a:2:{s:6:"memory";a:5:{s:5:"total";i:4139868160;s:4:"free";i:1306845184;s:7:"buffers";i:74797056;s:6:"cached";i:2103566336;s:4:"used";i:2833022976;}s:4:"swap";a:3:{s:5:"total";i:8389742592;s:4:"free";i:8389742592;s:4:"used";i:0;}}
During the UNSERIALIZE function on the 32bit system the bitcode is lost
and the number became negative.
Reproduce code:
---------------
serialize this object on different OS:
[mem] => Array
(
[memory] => Array
(
[total] => 4139868160
[free] => 1331732480
[buffers] => 68988928
[cached] => 2102939648
[used] => 2808135680
)
[swap] => Array
(
[total] => 8389742592
[free] => 8389742592
[used] => 0
)
)
you'll get different SERIALIZED string that are not OS indipendent.
Expected result:
----------------
I expected that the object could be pass throug PHP servers
indipendently from the OS bit system.
Actual result:
--------------
The actual result is a serialized string not indipendent from OS, i
think i'll use JSON functions instead of serialize / unserialize.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=46882&edit=1
