Hello,
Ok, I already saw that the counters can have very large values by
looking at the signature :)
memcached_return_t memcached_increment(memcached_st *ptr,
const char *key, size_t
key_length,
uint32_t offset,
uint64_t *value);
My question was : are there any logical considerations in choosing
uint64_t for the counter value, instead of int64_t ? In my current
application, negative counters would be very handy, but unfortunately
memcached does not allow this. :(
Regards,
Vlad
On Oct 10, 8:03 pm, dormando <[email protected]> wrote:
> > Hello,
>
> > I see from the API that the memcached counters are unsigned long
> > integers.
> > My questions is : why unsigned ? Is there any possibility to use
> > signed integer counters with memcached ?
>
> > Regards,
> > Vlad
>
> The counters are documented in the server's doc/protocol.txt (most of
> them...). Some are signed, and it's usually explained as to why.
>
> But for the most part they only count upwards, and can be astronomically
> large. So 64bit they are...
