There's a difference between tendis flushdb and redis flushdb

[mozz85]

Description

according to this document， redis flushdb will only delete the keys of the currently selected DB。 https://redis.io/commands/flushdb/

while tendis delete all keys in all db。

127.0.0.1:51002> set 1 1
OK
127.0.0.1:51002> set 2 2
OK
127.0.0.1:51002> keys *
1) "1"
2) "2"
127.0.0.1:51002> select 4
OK
127.0.0.1:51002[4]> keys *
(empty list or set)
127.0.0.1:51002[4]> set 3 3
OK
127.0.0.1:51002[4]> flushdb
OK
(0.87s)
127.0.0.1:51002[4]> keys *
(empty list or set)
127.0.0.1:51002[4]> select 0
OK
127.0.0.1:51002> keys *
(empty list or set)
127.0.0.1:51002>

Expected Behavior

I think it should be noted in the document

[raffertyyu]

Due to the huge difference in system architecture between tendis and redis, implementing a flushdb command similar to redis is a very expensive behavior with low practical value.

Thanks for pointing out the lack of documentation about this. We will add relevant content soon.