Relinq VS LiteDB

First attempt was pretty awful... Believe it or not, writing a LINQ provider can be hard. I made a break and investigated further, how existing ORMs and Marten are implementing LINQ providers. Library that some of the ORMs are using (or were using) is called relinq. Documentation isn't great but there a a couple of examples on how to use it. Reqlinq separates single LINQ expression into multiple expressions (where, select, order, ...) Armed with new awesome library I decided to have another go on writing my own little DAL library with SQLite as a store. It is far from complete, it doesn't yet have async operations, it is missing LINQ transformations in Select expression, performance is bad (like 10x slower than EF Core with SQLite),... there is a lot of work left to be done.

The best way to go about it seemed to be using Remotion’s relinq. I even managed to find one example to base my work off.

Well, there are LINQ Parsing pipelines out there, namely ReLinq.

Personally, I used to use LiteDB which is a NoSQL version which in v4 paired very nicely with F# thanks to Zaid's lovely LiteDB.FSharp library. Sadly, when v5 showed up, a lot of the F# niceties were lost given how the API was changed and v5 was not very F# friendly. You can still use it of course but you fall back to more unsafe F# code which is not ideal.

Maybe you want LiteDB? I don't think you need to write SQL, you can interact with the API.

Are you aware of LiteDB? It seems like your project is going for a very similar niche. Most people looking for this type of thing will probably go for the more mature and feature-rich solution (LiteDB). So if your project has some unique value proposition to distinguish it from LiteDB, you should elaborate on that.

Please consider using the primary key to generate an unique value on the db side.

LiteDB

Before checking this out, people might want to take a look through the issues and pull requests of which there are 500+ and 50+ respectively [1]. I was really optimistic about this project and it was headed in a great direction, but it's not in a production ready state, and it seems that the main guy behind it has decided to move onto other things. It's been about a year since there was any significant activity.

I just mention this because a lot of these little issues might only become more apparent after integrating the db into your project and so it can be a bit annoying. I ended up swapping to Linq2DB [1]. It's something, more or less, similar offering an ORM/LINQ type system as well as the ability to also use direct SQL if desired. But the neat thing is that it also uses a standardized API for the LINQ query language, so you can do things like swap from SQLite to PostgreSQL in one* line of code, so long as you're not using any provider specific extensions.

[1] - https://github.com/mbdavid/LiteDB

[2] - https://github.com/linq2db/linq2db

A mature NoSQL embedded/flatfile database like LiteDB would be nice. There are some similar Rust libraries but they aren't very close to production ready and the API tends to not be too user friendly. I had trouble finding one of these for a small app I had to write recently.