Unit test for delete(String, int) fails about spymemcached

[GoogleCodeExporter]

This is a documentation bug.  Memcached's integer parameter to delete is used 
to tell
memcached how long the key should be reserved as to prevent adds.

The following is my test for this:

    public void testDelayedDelete() throws Exception {
        assertNull(client.get("test1"));
        client.set("test1", 5, "test1value");
        assertEquals("test1value", client.get("test1"));
        client.delete("test1", 5);
        assertNull(client.get("test1"));
        // Add should fail, even though the get returns null
        client.add("test1", 5, "test1value");
        assertNull(client.get("test1"));
        // Replace should also fail
        client.replace("test1", 5, "test1value");
        assertNull(client.get("test1"));
        // Set should be fine, though.
        client.set("test1", 5, "test1value");
        assertEquals("test1value", client.get("test1"));
    }

Original comment by [email protected] on 12 May 2008 at 5:01

• Added labels: Component-Docs, Milestone-Release2.1

[GoogleCodeExporter]

Docs fixed in 9de48599d5a18cb5d59779e7c28713b517285aa4

Original comment by [email protected] on 14 May 2008 at 5:41

• Changed state: Fixed