Changes between Version 1 and Version 2 of Ticket #15458, comment 16
- Timestamp:
- 08/01/2011 04:09:49 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15458, comment 16
v1 v2 1 I'm not sure about the best way of handling large custom fields, but I do know that we can reduce the memory footprint inhalf:1 I'm not sure about the best way of handling large custom fields, but I do know that we can reduce the memory footprint by half: 2 2 3 3 Currently, each field is stored twice: once in WP_User->data and once on the WP_User object directly. We can avoid this by using magic methods. So that's what [attachment:15458.diff] does.