I might be okay with this proposal. Any obvious downsides I'm missing? Recently I added a change so a SET which results in a memory failure will internally delete an existing value, for similar-but-not-similar data bug issues.
If no one can think of any downsides and I don't find one while implementing it, I'll attempt to queue this change for 1.2.7. Patches welcome too :P -Dormando > Yeah, pros and cons both ways. Another proposal, just for fun: we could > return NOT_FOUND (pro: no change to clients!) when it's not a number, and > _also_ delete the value. So no "get" surprises later. :-) > > But let's do something .... the current behavior is strange for no good > reason. I doubt anybody's relying on it. > > - Brad >
