-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoff,
I looked at the string.
s:1745:"s:1735:"s:1725:"s:1715:"s:1705:"s:1695:"s:1685:"s:1675:"s:1665:"s:1655:"s:1645:"s:1635:"s:1625:"s:1615:"a:2:{
see all of the s's? It means that unserializer will produce a string that
looks like was not unse
To: [EMAIL PROTECTED]
Subject: [PHP] Unserialize stopped working after php & db upgrade
Paul,
PN> It looks like that string has been serialized multiple times
Many thanks - that is the problem! I think that this qualifies as one
of my more creative bugs...
Can I ask you how you spotted this? P
Paul,
PN> It looks like that string has been serialized multiple times
Many thanks - that is the problem! I think that this qualifies as one
of my more creative bugs...
Can I ask you how you spotted this? Pretty impressive, considering you
only had the string itself to go on.
Thanks again,
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
There must be an error in the serialized stringswould you mind posting
one for us to look at? How about posting some code?
~Pauly
On Wednesday 18 September 2002 02:02 pm, you wrote:
> Hi folks
>
> Bit of a major panic - any help MUCH apprec
Hi folks
Bit of a major panic - any help MUCH appreciated.
I have been storing serialized arrays in MySQL Gemini tables without
any problems.
But with Gemini looking more and more like a dead duck, I decided to
take the server down and port from Gemini to InnoDB. I also took the
opportunity to
5 matches
Mail list logo