[Bb-trac] Re: [bbPress] #995: performance design flaw in bb_update_meta

[bbPress]

#995: performance design flaw in bb_update_meta
----------------------+-----------------------------------------------------
 Reporter:  _ck_      |        Owner:                    
     Type:  defect    |       Status:  new               
 Priority:  normal    |    Milestone:  1.0-beta & XML-RPC
Component:  Back-end  |      Version:  0.9.0.2           
 Severity:  normal    |   Resolution:                    
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by sambauers):

 INSERT ... ON DUPLICATE KEY may be an option if we decide not to do
 anything with the idea in #629, basically doing this closes that door
 pretty much completely. I'm happy to have a conversation about the merits
 of that other ticket as well.

 The second part (from the previous comment) about reloading the topic is
 quite necessary I think. Firstly, updates don't happen all that often and
 secondly, the only sure fire way to make sure your cache matches your
 database after an update is to read from the database again. Considering
 that topics and their meta are stored as one object in the object cache,
 the rereading is required unless we create some way to selectively update
 parts of the cached objects. But since the object cache is fairly generic
 and... well... dumb, it doesn't have anything like that. In the end
 rereading is a lot easier from a maintenance of code perspective.

-- 
Ticket URL: <http://trac.bbpress.org/ticket/995#comment:2>
bbPress <http://bbpress.org/>
Innovative forum development