LiteDB
SqlKata Query Builder
Our great sponsors
LiteDB | SqlKata Query Builder | |
---|---|---|
11 | 5 | |
8,161 | 2,978 | |
- | 1.5% | |
8.0 | 3.0 | |
1 day ago | 6 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LiteDB
-
Local migrations for embedded SQLite in F#
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.
-
Yet another embedded DB (kind of)
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.
-
How to introduce a queue for my API.
Looks like LiteDb is thread safe so it would be useful to see the error stack and the exact error message.
Please consider using the primary key to generate an unique value on the db side.
-
Unity MVVM
LiteDB
-
LiteDB: A .NET embedded NoSQL database
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.
One reason:
SQLite is slower than LiteDB in this benchmark project created by the LiteDB inventor
https://github.com/mbdavid/LiteDB-Benchmark
https://github.com/mbdavid/LiteDB/issues/291
Another (lesser) reason is the similarity to MongoDB methods, if that's what you are used to it will feel familiar, but no MongoDB server needed.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
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.
SqlKata Query Builder
-
EF Core or Dapper
SqlKata is your friend.
-
ASP.Net Core database modelling without using existing ORMs?
Don't know if can be a good pick for the no-ORM requirement but I would take a look at SqlKata which is a nice query builder + execution engine, built on top of Dapper
-
Windyquery: A non-blocking Python PostgreSQL query builder
That is basically the description of an object mapper, with all the guarantees of an object mapper :). It seems if you actually use the query builder as such, no guarantees exist.
I'm pretty picky regarding query builders and ORM's, to the extent of having written several of them over the years, in different languages (both dynamic and strong typed, unfortunately closed-source). I'm a strong advocate of schema-first design, and usually a query builder will allow you to design your queries explicitly, but having some internal behaviors (such as string concatenation, identifier quoting and automatic in-order separation of parameters and values to be bound) taken care of. As good examples of this, I'd mention golang's goqu (https://github.com/doug-martin/goqu) and - to some extent - C# SqlKata (https://sqlkata.com/). Following my frustrations with Python ORMs, I built my own toy project, sort-of-in-beta, called rickdb (https://github.com/oddbit-project/rick_db).
-
I don't want to learn your garbage query language
Less about the exact syntax and more about the tool, for example: https://github.com/sqlkata/querybuilder. I just chose that since it was on top of a search but the idea is the same. Your code generates raw SQL, so it's 100% interchangeable with writing SQL yourself however the builder library deals with the syntax, proper ordering, quoting, full attribute names, etc. Some such libraries even let you define your schema in code to make your SQL generation type safe.
What are some alternatives?
RavenDB - ACID Document Database
MongoDB - The MongoDB Database
Realm Xamarin - Realm is a mobile database: a replacement for SQLite & ORMs
Apache Ignite - Apache Ignite
Event Store - EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures
DBreeze - C# .NET NOSQL ( key value store embedded ) ACID multi-paradigm database management system.
Yessql - A .NET document database working on any RDBMS
NReco LambdaParser - Runtime parser for string expressions (formulas, method calls). Builds dynamic LINQ expression tree and compiles it to lambda delegate.
Insight.Database - Fast, lightweight .NET micro-ORM
BrightstarDb - This is the core development repository for BrightstarDB.