LINQ to DB
Norm.net
LINQ to DB | Norm.net | |
---|---|---|
20 | 11 | |
2,860 | 175 | |
0.5% | 0.0% | |
8.8 | 8.3 | |
3 days ago | about 1 month 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.
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
Norm.net
-
Dapper is die?
You can use Norm: https://github.com/vb-consulting/Norm.net
-
ASP.Net Core database modelling without using existing ORMs?
If you don't like writing PostgreSQL functions, that's fine, I can recommend this Micro ORM https://github.com/vb-consulting/Norm.net or Dapper which is currently way more popular. Still, pgroutiner can help you juggle all those scripts.
- Do you have a preference between Entity Framework and Dapper?
-
Dapper is it worth using now with the improvements in EF in dotnet 6?
If you want dapper-like library that supports iasyncenumerable properly you can try out Norm https://github.com/vb-consulting/Norm.net
- Mapping raw SQL query results to anonymous types
-
I think I've managed to beat Dapper in performances
It looks like it even performs better: https://github.com/vb-consulting/Norm.net/blob/master/PERFOMANCE-TESTS.md
- Is there any dapper (micro-orm) enthusiast?
- Is Dapper ready for .NET 6?
- 100 stars in Github - Dapper Query Builder using String Interpolation
-
Contributing to the No Object Relational Mapping Project (NORM) for PostgreSQL
Now, it maybe is unrelated, but, I have another bit unrelated project which is a micro ORM for the .NET that is called exactly the same. Norm: https://github.com/vb-consulting/Norm.net
What are some alternatives?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Dapper.SimpleCRUD - Who wants to write basic read/insert/update/delete statements? SimpleCRUD provides simple CRUD helpers for Dapper.
MongoDB Repository pattern implementation
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
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.
NORM - NORM - No ORM framework
RepoDb - A hybrid ORM library for .NET.
DapperQueryBuilder - Dapper Query Builder using String Interpolation and Fluent API
NHibernate - NHibernate Object Relational Mapper
pdd-demo - PostgreSQL Driven Development Demo Web Application With PgRoutiner, .NET and Svelte