memcache(3) 1.2.0 released...

John McCaskey johnm at
Wed Jan 12 11:15:50 PST 2005

On Wed, 2005-01-12 at 22:03 +0300, Antony Dovgal wrote:
> On Wed, 12 Jan 2005 11:02:01 -0800
> John McCaskey <johnm at> wrote:
> > If the get() command however returns a FALSE for either my stored
> > FALSE value or for a miss, then I will always have to assume its a
> > miss and hit the slow storage everytime I retrieve a FALSE.  Am I
> > missing something here?  I can't see it if so.
> Yup, you're missing "===" operator.
> empty string == false, but empty string !== false.

Sure, but an empty string is not the same as a FALSE if I am storing
both and considering them distinct.  I know about ===.  But I want to
get exactly what I store back from memcached, if I store an '' or a
FALSE then I should get exactly a '' or a FALSE in return and when I
test with === it should match up.

With returning a single value and no error code indication this is
simply not possible as whatever the sentinel that indicates a miss is
can now not be stored and retrieved reliably.  This is clearly a rare
situation, but I think it's important to support.

John A. McCaskey
Software Development Engineer
Klir Technologies, Inc.
johnm at

More information about the memcached mailing list