-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
mizusumashi wrote:
Brion Vibber wrote:
No as it contains private data, but we can check
the encoding ourselves
once we've gotten in there.
I see. Thank you for the reply.
Ok, I believe we've tracked it down -- the data came through fine from
PayPal, and into our primary databases, but got corrupting during
copying from the primary database to the reporting database.
The corruption appears to have been due to a temporary variable in the
trigger script using the default server encoding (Latin-1) instead of
the encoding of the related databases (UTF-8).
I've updated the trigger to define the charset on the variable, which
should hopefully fix it for new entries, and have rebuilt the reporting
database so old entries are now correct.
- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iEYEARECAAYFAkk1lRMACgkQwRnhpk1wk46JsACePU0Tzq0bxxuxdhBCsMkuV/aP
/0kAoMaYd8TZYT3MX/6EATugpJt3Bmkb
=T1CB
-----END PGP SIGNATURE-----