Once #839444: Make serializer customizable for Cache\DatabaseBackend is committed we should swap the serializer configured for DatabaseBackendFactory from PHPSerialize to IgbinarySerialize.

CommentFileSizeAuthor
#2 2836091.patch723 bytesmkalkbrenner

Comments

mkalkbrenner created an issue. See original summary.

mkalkbrenner’s picture

Status: Active » Needs review
StatusFileSize
new723 bytes
andypost’s picture

Version: » 8.x-1.x-dev

Why you need such hack instead of changing serializer at PHP level? It looks like tremendous overhead for build-in operation

fabianx’s picture

socialnicheguru’s picture

Per @andypost I do not need this patch if I update my services.yml to use the proper serializer. Is my interpretation correct?

mkalkbrenner’s picture

No. You can do everything in your site specific services.yml.
This patch was just a convenience function.

andypost’s picture

Status: Needs review » Reviewed & tested by the community

As core 11.0/10.3 has serializer configurable #839444: Make serializer customizable for Cache\DatabaseBackend

maybe it needs follow-up to fix arguments

grimreaper’s picture

Hello,

As the 8.x-1.x branch is no more supported and as the 2.0.x module has a different approach, is this issue still relevant? Could it be closed?

socialnicheguru’s picture

D10.3/11 added #839444: Make serializer customizable for Cache\DatabaseBackend.
Does it have any impact on this module version 2.x?

andypost’s picture

I think we need to add PECL extension to CI images to make ball roll

andypost’s picture

now all 8.3-8.5 images has igbinary PECL enabled