The system currently sorts comparing raw byte values directly. So if I'm understanding correctly, no it doesn't handle unicode sorting. If key's were stored as strings and compared that way, yes. :)
There are examples with integration tests currently.
The website explains some tadbits regarding concurrency quite well.
I'd need to better understand what you mean.
I do agree, much to prove still.
If you want feel free to join the Discord and we can talk in real-time. Could be a diverse and interesting conversation.
I've thought about this more than I'd like to admit. I'd need to review if it's possible to refactor a bit to work with C99+. I don't believe there would be many changes but it's been awhile writing the entire code base as it is.
Because TidesDB is in BETA v0.8.0 currently we can definitely do this. I'm curious do you use CMake? I will create an issue.
Concerning cmake: I only use it if unavoidable; instead I implemented my own build system (https://github.com/rochus-keller/busy/) some years ago which I now use for most of my personal projects.
You are quite the master I'm very similar to you in that I gotta get my hands on everything haha.
I tagged yeah on the issue. I will after work have a look at the changes required to make backwards compatible. If not much, why not. I'll weigh the possible negatives if any.