fix encode string as integer

[michael2008]

encoder should be strict about the strings that can be encoded as integer.
as strconv.ParseInt() is not accurate for this case, we need to check the string content and pick up
the "pure" uint32 or uint64 numbers.

Also the WriteSetObject() function has a wrong state to fix.

Fix issue #38
Fix issue #40

[HDT3213]

I will review it later today

[HDT3213]

Actually, -1 should be encoded as int

127.0.0.1:6379> set a -1
OK
127.0.0.1:6379> object encoding a
"int"

[michael2008]

Actually, -1 should be encoded as int

127.0.0.1:6379> set a -1
OK
127.0.0.1:6379> object encoding a
"int"

I read some rdb libs where decoders read uint. so encoder better only encodes uint too.

[HDT3213]

For your information, redis use string2ll to determine whether int encoding can be used.

[HDT3213]

Actually, -1 should be encoded as int

127.0.0.1:6379> set a -1
OK
127.0.0.1:6379> object encoding a
"int"

I read some rdb libs where decoders read uint. so encoder better only encodes uint too.

Let me think about it

[HDT3213]

rdbtools supported signed int32 too. I prefer to follow the redis official strategy.

https://github.com/sripathikrishnan/redis-rdb-tools/blob/master/rdbtools/parser.py#L494

[michael2008]

rdbtools supported signed int32 too. I prefer to follow the redis official strategy.

https://github.com/sripathikrishnan/redis-rdb-tools/blob/master/rdbtools/parser.py#L494

ok. but the encoder and decoder should be modified accordingly. current codes only support uint.

[HDT3213]

rdbtools supported signed int32 too. I prefer to follow the redis official strategy.
https://github.com/sripathikrishnan/redis-rdb-tools/blob/master/rdbtools/parser.py#L494

ok. but the encoder and decoder should be modified accordingly. current codes only support uint.

Although the code is a bit strange, it does work for negative numbers.😂 I'll sort it out.
https://github.com/HDT3213/rdb/blob/master/core/string.go#L92