[wp-trac] [WordPress Trac] #23381: update_option() stores unserialized value in object cache

[WordPress Trac]

#23381: update_option() stores unserialized value in object cache
--------------------------+------------------
 Reporter:  rmccue        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.6
Component:  Cache         |     Version:  3.1
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |
--------------------------+------------------
Changes (by hexalys):

 * cc: themacmaster@… (added)


Comment:

 Replying to [comment:3 rmccue]:
 > As per rboren on IRC, changed the patch to switch `add_option()` to
 match `update_option()`. Will require fixing APC to handle the specific
 use-case.

 rmccue, could you explain the rationale for switching add_option() to
 match update_option(), rather that the other way around. This would leave
 an inconsistent pattern of 'alloptions' being either a serialized string
 or an array depending on the existence of an object cache, like it it now
 with the r13673 defect. I am not liking the idea of having mixed variables
 with a context dependency added. Update_option() is the one that should
 match add_option() for consistency in my view. That's where it was broken
 in the first place.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23381#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software