Strongly recommend upgraded your version of memcached NOT_STORED means just that, your data was not stored. If you are using the add command to store data, this means that there's already data under that key. If you are using replace it means that there's not data under that key.
You probably mea set.
Strongly recommend upgraded your version of memcached. NOT_STORED means just that, your data was not stored. If you are using the add command to store data, this means that there's already data under that key.
If you are using replace it means that there's not data under that key. You probably mea set.
Thanks and sorry for the late reply. The problem was two-fold. Using Serializable was not adequate for some objects so we have to implement ISerializable.
We were also using ADD rather than SET. From memory I couldn't find an upgrade for memcached and once we fixed the above it worked. Cheers.
I had this problem to...I was running something like: var = CACHE. Fetch("key_name",1. Day,true) do ModelName.
Find_by_id(id) end So I was having active record find a record for me but I didn't know that memcached doesn't store nil values. What was happening was active record was returning nil because it couldn't find the record and therefore I was telling memcache to store a nil value. The fix was simply this: var = CACHE.
Fetch("key_name",1. Day,true) do ModelName. Find_by_id(id) || "" end I use Ruby to code with.
Hope this helps.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.