key-value

What happened?

Not really a bug, but maybe unexpected behavior. Since etcdctl del accepts an optional second parameter which deletes all keys in a range, these are very easy mistakes to make:

# Oh no, there was a space in the key I copied!
etcdctl del /registry/persistentvolumes/pvc-eef4ec4b-326d-47e6- f11c-6474a5fd4d89
# <deletes thousands of keys>

etcdctl put 'key s

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect

getset应该是原子操作吧，这么实现并发读写就有问题了

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients