DotNet-ORM-Cookbook
Sequel
DotNet-ORM-Cookbook | Sequel | |
---|---|---|
9 | 36 | |
334 | 4,899 | |
0.9% | - | |
0.0 | 8.9 | |
almost 2 years ago | 25 days ago | |
C# | Ruby | |
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
Sequel
- Ruby Sequel Google group banned
- Ask HN: What is your go-to stack for the web?
-
Ruby 3.3
Some of the most enlightening books I’ve read when I was first learning Ruby were Text Processing in Ruby, and Building Awesome Command Line Apps in Ruby 2. They each reveal certain features and perspectives that work towards this end, such as text parsing moves, Ruby flags to help you build shell 1-liners you can pipe against, and features with stdio beyond just printing to stdout.
Then add in something like Pry or Irb, where you are able to build castles in your sandbox.
Most of my data exploration happens in Pry.
A final book I’ll toss out is Data Science at the Command Line, in particular the first 40 or so pages. They highlight the amount of tooling that exists that’s just python shell scripts posing as bins. (Ruby of course has every bit of the same potential.) I had always been aware of this, but I found the way it was presented to be very inspirational, and largely transformed how I work with data.
A good practical example I use regularly is: I have a project set up that keeps connection strings for ten or so SQL Server DBs that I regularly interact with. I have constants defined to expedite connections. The [Sequel library](https://sequel.jeremyevans.net/) is absolutely delightful to use. I have a `bin/console` file that sets up a pry session hooking up the default environment and tools I like to work with. Now it’s very easy to find tables with certain names, schemas, containing certain data, certain sprocs, mass update definitions across our entire system.
```
-
Python: Just Write SQL
Thea answer to your prayers already exists: http://sequel.jeremyevans.net/.
By far the best database toolkit (ORM, query builder, migration engine) I have seen for any programming language.
-
Is ORM still an anti-pattern?
Ruby sequel (http://sequel.jeremyevans.net/) is the only library where you can combine classic ORM Model bases usage, with a more raw query builder "just get me all the data into plain objects". You'll never need anything again in your career life.
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
Sketch of a Post-ORM
If you want a db tool which can be an ORM for your app, and drop down to a lower level dsl, while targeting specific features of the databases it supports, + having a "composable superset for building queries", there's [ruby sequel](http://sequel.jeremyevans.net/), which is the best tool of the kind you'll get for any proglang. Everything the author wants, minus the typrchecking perhaps, which is IMO shooting at the stars.
-
There's SQL in my Ruby
I love the Sequel library from Jeremy Evans (so much better than Rails' AREL). I've used it as my ORM-of-choice since 2008. When leveraging Sequel I almost always use the DSL, but there are times that I want to use bare SQL. When that happens, I almost always use HEREDOCs and my own version of String#squish.
- Objection to ORM Hatred
-
ruby 3.2 unable to connect to database via odbc
sequel is a pretty good option! To use the above snowflake adapter for sequel, you'll have to learn to use sequel (which is pretty easy). https://sequel.jeremyevans.net/
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.
ROM - Data mapping and persistence toolkit for Ruby
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
ActiveRecord
DataAccessGeneration - Better SQL Server stored procedure calls from C#
DataMapper
squid - 🦑 Provides SQL tagged template strings and schema definition functions.
Hanami::Model - Ruby persistence framework with entities and repositories
Tortuga Chain - A fluent ORM for .NET
Redis-Objects - Map Redis types directly to Ruby objects
Neo4j.rb - An active model wrapper for the Neo4j Graph Database for Ruby.
Mongoid - The Official Ruby Object Mapper for MongoDB