Tortuga Chain
squid
Tortuga Chain | squid | |
---|---|---|
11 | 2 | |
335 | 130 | |
0.0% | - | |
6.1 | 0.0 | |
about 1 month ago | about 1 year ago | |
C# | TypeScript | |
GNU General Public License v3.0 or later | 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.
Tortuga Chain
- Resistance to use Entityframework !!
-
C# 11 Raw String Literals Explained
I mean, look at this mess: https://github.com/TortugaResearch/Tortuga.Chain/blob/main/Tortuga.Chain/Tortuga.Chain.SqlServer/shared/SqlServer/SqlServerMetadataCache.cs
- Does anyone know how I can return character length limits from a query?
- PostgreSQL 14 Breaks the .NET and Java Drivers for PostgreSQL - New features don't play nice with legacy workarounds
-
What was used before LINQ to SQL
Omg I didn’t realize this was you: https://github.com/TortugaResearch/Chain
-
"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.
-
Traits for C#
Here is a real example from the ORM that I built this for: https://github.com/TortugaResearch/Chain/blob/Traits/Tortuga.Chain/Tortuga.Chain.Access/Generated/Tortuga.Shipwright/Tortuga.Shipwright.TraitGenerator/Tortuga.Chain.Access.AccessDataSourceBase.cs
- Why most people use Dapper instead of EF Raw Queries?
- Check if a column allows nulls
- EF/Dapper vs Custom-developed ORM
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?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
ship-hold - data access framework for Postgresql on nodejs
LINQ to DB - Linq to database provider.
trilogy - TypeScript SQLite layer with support for both native C++ & pure JavaScript drivers.
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
stackql-middleware - Middleware solution to allow clients to query back end APIs using SQL
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.
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
SQLProvider - A general F# SQL database erasing type provider, supporting LINQ queries, schema exploration, individuals, CRUD operations and much more besides.
DotNet-ORM-Cookbook - This repository is meant to show how to perform common tasks using C# with variety of ORMs.
Dapper Extensions - Dapper Extensions is a small library that complements Dapper by adding basic CRUD operations (Get, Insert, Update, Delete) for your POCOs. For more advanced querying scenarios, Dapper Extensions provides a predicate system. The goal of this library is to keep your POCOs pure by not requiring any attributes or base class inheritance.
Sequel - Sequel: The Database Toolkit for Ruby