#6073 - We need a special field type for serialized data
| Identifier | #6073 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | We need a special field type for serialized data |
| Status | Completed |
| Tags |
Roadmap: v11 (custom) |
| Handling member | PDStig |
| Addon | core |
| Description | The privacy system needs to know which fields expect serialized data rather than raw strings. That way, it can properly parse them and maintain a serialized structure when anonymising instead of throwing "unknown" raw into the field (and causing corruption).
Add a new field type to Composr for this. Perhaps "SERIAL". Update across the board any fields that store serialized data. Consider allowing the database driver to automatically serialize and unserialize this data (e.g. on an insert or update, it will automatically serialize before storing, and unserialize before returning when querying for it). Also, consider using BLOB for this field type as per PHP: "Note that this is a binary string which may include null bytes, and needs to be stored and handled as such. For example, serialize() output should generally be stored in a BLOB field in a database, rather than a CHAR or TEXT field." |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments