LINQ to DB
sequelts
LINQ to DB | sequelts | |
---|---|---|
20 | 3 | |
2,860 | 28 | |
0.5% | - | |
8.8 | 0.0 | |
1 day ago | over 1 year ago | |
C# | TypeScript | |
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.
LINQ to DB
- Upserting complex data models from an API into EF Core entities
-
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.
[1] - https://github.com/mbdavid/LiteDB
[2] - https://github.com/linq2db/linq2db
-
Flyweight: An ORM for SQLite
I had a positive experience with Linq2db? https://github.com/linq2db/linq2db
I mention because I had something of the opposite experience with it. It not only ended up yielding the correct queries, but I saw a significant increase in performance. And the neat thing about it, beyond ORM and linq-to-sql, is a common interface amongst providers - so you can do things like swap from SQLite to Postgres with 1 line* of code, so long as you're not using provider specific extensions.
-
.NET 6 - ORM vs Stored Procedures - Azure Functions + SQL Databases
Temporary tables are covered by linq2db. But better to show Stored Proc maybe your final query just needs several CTE which also supported by linq2db.
-
LINQ to SQL
check this out as an alternative... https://github.com/linq2db/linq2db
-
Expression trees for LINQ
My learning path was supporting linq2db, not short way. StackOverflow was original source to find something like, how to do if operator in Expression Tree, how to throw exception in Expression Tree, how to build dynamic filter, ect.
-
Dapper is it worth using now with the improvements in EF in dotnet 6?
Checkout linq2db No need for Dapper or EF with this library. I wouldn't want to miss it.
- What is the best PostgreSQL ORM tool for use in a .NET Framework 4.7 application?
-
SchemaTypist: Entity generator for Dapper and SqlKata
Why not linq2db? Faster than Dapper and has LINQ support.
-
EF Core is good for most things.
Probably you can understand why linq2db was born 15 years ago
sequelts
-
Kysely: TypeScript SQL Query Builder
You can use these template literal types + infer to build an entire SQL parser. I did a POC that infers SQL query types by parsing the SQL query on a type level:
https://github.com/nikeee/sequelts
However, building this parser is pretty cumbersome and supporting multiple SQL dialects would be lots of pain. While I'm not a fan of query builders per se, Kysely pretty much covers everything that my POC tried to cover (except that 0 runtime overhead). However, you get the option to use different DBMs in tests than in production (pg in prod, sqlite in tests), which is a huge benefit for a lot of people. sequelts was designed to work with sqlite only. And it's not a hack.
-
Flyweight: An ORM for SQLite
The only thing I can imagine where this would be useful is when you don't have control about what DB is being used, for example, when building a product that should be compatible with Postgres and MariaDB (and each is getting used). However, in the age of containerization, this isn't a big problem any more.
In some ORMs, I need to create types that the result of a query containing JOINs is mapped to. Others don't support them _at all_. In TypeORM, there is a query builder which forces you to put in _some_ SQL for things like "WHERE a in (b, c)".
I created a proof of concept of a different approach: Just embrace SQL and provide static typing based on the query. The return type of a query is whatever that thing is that the query returns in the context of the database schema. It's possible to do in TypeScript, by parsing the SQL query at development time:
https://github.com/nikeee/sequelts
One benefit is that it does not need any runtime code, as it's just a type layer over SQL. You don't have to rely on some type-metadata that TypeScript emits. That's why it also works with JavaScript only.
-
Deepkit – High-Performance TypeScript Framework
I don't like ORMs that use runtime types either. Most of the time, I want to write raw SQL.
So as an experiment, I created a library that statically types raw SQL:
https://github.com/nikeee/sequelts
The idea is to parse the SQL queries using TS's type system. The parsed query is combined with the database schema and therefore, we know what type the query will return.
This is especially useful due to TS's structural type system.
What are some alternatives?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
liveviewjs - LiveView-based library for reactive app development in NodeJS and Deno
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
flyweight - An ORM for SQLite
MongoDB Repository pattern implementation
kysely-codegen - Generate Kysely type definitions from your database.
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
ts-sql - A SQL database implemented purely in TypeScript type annotations.
RepoDb - A hybrid ORM library for .NET.
assert-combinators - Functional assertion combinators.
NHibernate - NHibernate Object Relational Mapper
postgresql-typed - Haskell PostgreSQL library with compile-time type inference