moor VS Hive

I think Haskell or OCaml would do a better job on the ADTs for a parse tree. When doing this, I found Rust's enums... anemic... and got very annoyed by the awkwardness of having to Box recursive types. I was reaching for the ability to continue to be able to pattern match on nodes while attaching common attributes (line numbers, etc.) and ended up having to bury everything 1 level deep in a struct which ended up feeling awkward.

That and Rust's iterators are terrible at introducing ownership agony.

In any case, I've ... done it (https://github.com/rdaum/moor/blob/main/crates/compiler/src/...) but can't say I liked it.

I do really like "pest" as a parser generator though.

See: https://github.com/rdaum/moor

I've been working on a rewrite of the server into Rust, for kicks: https://github.com/rdaum/moor

Unfortunately still lots of work there to be done, and I have no time.

The extension by default does not save any state, so we can use local storage like hive DB it's a NoSQL DB for flutter which actually stores data in Indexed DB in browser

Even the Hive readme recommends Isar https://github.com/hivedb/hive

I'm trying to learn new database for my app, it's called HiveDB (the database, not my app). In their docs, they mentions a lot about "lexicographical order". I tried to read the explanation on Wikipedia and answers from Stackoverflow but it still doesn't make any sense for me. What is that actually?

Hive is popular but there was an issue which was closed just a month ago after 2 whole years. An issue like this would be a disaster for a primary database

Here's type registry implementation code in hive if you want to check.

hive is a lightweight key-value database written in Dart for Flutter applications, inspired by Bitcask.

I'm using HiveDB for the history part, I thought I'd use SQLite, but I decided to try something I didn't know (and don't use at work)

Moor is a well-maintained ORM for sqlite3, a relational database management system. Hive is a fast but buggy key-value store. It's not an apple to apple comparison, they serve different purposes. Make the choice based on the type of data you want to store and how you need to access it.