DotNet-ORM-Cookbook
squid
| DotNet-ORM-Cookbook | squid | |
|---|---|---|
| 9 | 2 | |
| 334 | 130 | |
| 0.9% | - | |
| 0.0 | 0.0 | |
| almost 2 years ago | about 1 year ago | |
| C# | TypeScript | |
| The Unlicense | 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.
DotNet-ORM-Cookbook
- Dapper vs. Entity Framework With Postgres
-
How do you do DB crud for your .NET apps? EF? Dapper? ADO.NET?
ORM Cookbook: https://tortugaresearch.github.io/DotNet-ORM-Cookbook/
- What is the best PostgreSQL ORM tool for use in a .NET Framework 4.7 application?
-
What was used before LINQ to SQL
Here is a list of examples using ADO and NHibernate. https://tortugaresearch.github.io/DotNet-ORM-Cookbook/
-
"ORMs have a special place in my heart, not entirely unlike Brutus and Caesar: a dear friend who betrays you and leaves you to die a slow, painful death." – Taming SQL and ORMs with sqlc
You can see a comparison in the ORM Cookbook. https://tortugaresearch.github.io/DotNet-ORM-Cookbook/ and this (out of date) post https://github.com/TortugaResearch/Chain/wiki/A-Chain-comparison-to-Dapper.
- Alternatives to EF.Core
-
Why most people use Dapper instead of EF Raw Queries?
The .NET ORM Cookbook revealed some areas where it could be improved. https://github.com/TortugaResearch/DotNet-ORM-Cookbook
-
Warning about Dapper + PostgreSQL in .NET 6
I was really surprised when I updated the ORM Cookbook to .NET 6 and saw this. If you want to play with the code, it is at... https://github.com/Grauenwolf/DotNet-ORM-Cookbook
squid
-
Don't use your ORM entities for everything – embrace the SQL
I guess I failed to set the context correctly given that you presented solutions for Clojure and Python, where it isn't as much of a problem since from the start the language fails to provide compiler guarantees you usually come to expect out of a SQL driver wrapper in typed languages (even though Clojure macros are probably powerful enough to allow this).
As a comparison, DX-wise this is no safer and is indeed very similar to the usual idiom in Go for example, where you just concatenate (pre-interpolated) SQL strings. But when you actually want the compiler to prove the correctness of your queries even in a rudimentary way, these .sql file solutions usually (if not, everytime) fail to provide the necessary external checker that processes templates and uses an accurate model of your database and SQL to verify that all used combinations make sense.
The closest thing to a proper take on this I've seen is https://github.com/andywer/squid with https://github.com/andywer/postguard which, although the SQL is inlined in the code, it uses the right approach for verifying correctness as far as I could tell in the little time I experimented with it.
-
"ORMs have a special place in my heart, not entirely unlike Brutus and Caesar: a dear friend who betrays you and leaves you to die a slow, painful death." – Taming SQL and ORMs with sqlc
For typescript and javascript, there's also squid + its companion project, postguard: https://github.com/andywer/squid
What are some alternatives?
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
ship-hold - data access framework for Postgresql on nodejs
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
trilogy - TypeScript SQLite layer with support for both native C++ & pure JavaScript drivers.
DataAccessGeneration - Better SQL Server stored procedure calls from C#
stackql-middleware - Middleware solution to allow clients to query back end APIs using SQL
Sequel - Sequel: The Database Toolkit for Ruby
Tortuga Chain - A fluent ORM for .NET