Setting arrays

[odino]

@waqasiqrar and me were looking at the set api, which doesnt allow to pass arrays.

We are converting arrays to json_encoded strings, is this the expected strategy or would you suggest anything else?

(just thinking if we're missing something)

[nrk]

Hi @odino,

as explained in #29, Predis doesn't perform any kind of serialization or deserialization of complex values as the library tries to stick with only what the commands actually do in Redis (or what the best practices described in the Redis docs say) in order to avoid unexpected or unwanted behaviours, leaving additional or more complex features to higher-level abstractions built upon the standard commands.

You can either serialize your values before passing them to set and deserialize them when fetching values back with get, or register two new virtual commands on the client such as setjson and getjson: doing so won't mess with the standard set and get commands and your code will be more self-explanatory.

Since the code in #29 is based on an older versions of Predis, I'll give you a more up-to-date snippet based on v0.8 using client options:

class StringSetJson extends Predis\Command\StringSet
{
    protected function filterArguments(Array $arguments)
    {
        $arguments[1] = json_encode($arguments[1]);
        return $arguments;
    }
}

class StringGetJson extends Predis\Command\StringGet
{
    public function parseResponse($data)
    {
        return json_decode($data, true);
    }
}

$client = new Predis\Client('tcp://127.0.0.1:6379', [
    'profile' => function ($options, $option) {
        $profile = Predis\Profile\ServerProfile::getDefault();
        $profile->defineCommand('setjson', 'StringSetJson');
        $profile->defineCommand('getjson', 'StringGetJson');

        return $profile;
    }
]);

$client->setjson("json_key", array(1,2,3,4));
$value = $client->getjson("json_key");

var_dump($value);

[odino]

thx man!