Closed (fixed)
Project:
Memcache API and Integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Mar 2011 at 09:13 UTC
Updated:
13 Jun 2011 at 06:22 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
drewish commentedThis seems like a dupe of #1101374: Remove warnings and notices. it's got a bunch of unrelated changes. I'm a bigger fan of this patch.
Comment #2
fgm#1101374: Remove warnings and notices. indeed contains 3 changes:
- the 0 argument, like in this one
- a warning removal to work around tiny incompatibilies between some combinations of the memcache extension and memcached daemon
- a bit of refactoring on return value, no functional change
Comment #3
Anonymous (not verified) commentedHere is the patch for 6.x-1.8 and 6.x-1.x-dev versions
Comment #4
Anonymous (not verified) commentedSorry, here are the patches without prefixing.
Comment #5
Anonymous (not verified) commentedWithout this patch, if you run memcached 1.4.5, you'll notice weird behavior with CCK. When you try to update content, the database will have the new value in it, but fields will display old content. To your users it looks like you can't edit/change content. What is happening is that memcache can't delete it's cache, so it continues to serve up stale content.
Comment #6
catchCommitted to 6.x-1.x, moving to D7.
Comment #7
Anonymous (not verified) commentedHere is the patch ported to 7.x-1.x-dev
Comment #8
catchWill review later. Thanks for the re-roll.
Comment #9
catchCommitted to 7.x-1.x, thanks!