Change Details

Following on from {T323236}, where Message was serialized and stored in the Database... ConcatenatedGzipHistoryBlob is documented as >WARNING: Objects of this class are serialized and permanently stored in the DB. https://wiki.php.net/rfc/phase_out_serializable >In PHP 9.0 the Serializable interface will be removed and unserialize() will reject payloads using the C serialization format. Code needing to support both PHP < 7.4 and PHP >= 9.0 may polyfill the Serializable interface, though it will have no effect on serialization. At some point in the future (though, ideally before it potentially breaks), we should work out a migration/mitigation plan.

Following on from {T323236}, where Message was serialized and stored in the Database... ConcatenatedGzipHistoryBlob is documented as >WARNING: Objects of this class are serialized and permanently stored in the DB. https://wiki.php.net/rfc/phase_out_serializable >In PHP 9.0 the Serializable interface will be removed and unserialize() will reject payloads using the C serialization format. Code needing to support both PHP < 7.4 and PHP >= 9.0 may polyfill the Serializable interface, though it will have no effect on serialization. At some point in the future (though, ideally before it potentially breaks), we should work out a migration/mitigation plan, as we do call `serialize()` on `ConcatenatedGzipHistoryBlob` objects.

Following on from {T323236}, where Message was serialized and stored in the Database... ConcatenatedGzipHistoryBlob is documented as >WARNING: Objects of this class are serialized and permanently stored in the DB. https://wiki.php.net/rfc/phase_out_serializable >In PHP 9.0 the Serializable interface will be removed and unserialize() will reject payloads using the C serialization format. Code needing to support both PHP < 7.4 and PHP >= 9.0 may polyfill the Serializable interface, though it will have no effect on serialization. At some point in the future (though, ideally before it potentially breaks), we should work out a migration/mitigation plan, as we do call `serialize()` on `ConcatenatedGzipHistoryBlob` objects.