Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #55942, comment 24


Ignore:
Timestamp:
10/21/2022 07:52:09 PM (20 months ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55942, comment 24

    initial v1  
    1 Another option here (which I'm not fond off, but is a possible solution) would be to only add a `TINYINT` field to these tables indicating whether the data in the value field is serialized or not. That perhaps can be `0` for default/unknown, `1` for serialized, and maybe `2` for JSON encoded. This will reduce complexity and won't have back-compat problems, but will also miss the chance to further improve the options and meta APIs.
     1Another option here (which I don't particularly like, but is a possible solution) would be to only add a `TINYINT` field to these tables indicating whether the data in the value field is serialized or not. That perhaps can be `0` for default/unknown, `1` for serialized, and maybe `2` for JSON encoded. This will reduce complexity and won't have back-compat problems, but will also miss the chance to further improve the options and meta APIs.