Norm
ecto
Norm | ecto | |
---|---|---|
3 | 14 | |
22 | 6,006 | |
- | 0.4% | |
0.0 | 9.0 | |
10 months ago | 4 days ago | |
Python | Elixir | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
Norm
- Show HN: Sqlbind a Python library to compose raw SQL
-
Sketch of a Post-ORM
This is just not liking SQL, which is fine, but it's not 'the future of querying databases'. It's just a simplified language that is under-specified and doesn't really support even a fraction of the use cases of SQL, and therefore looks 'cleaner'. It's a bad abstraction.
Here is my attempt at a 'post orm' if anyone is interested, as a bonus it is fully implemented and some people actually use it: https://github.com/justinvanwinkle/Norm
-
Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs
I tried to do something similar with https://github.com/justinvanwinkle/Norm about 10 years ago. It hasn't generated a lot of interest, but I find it quite useful to construct queries without having to learn the minutia of an ORM library, or even a SQL generation library.
ecto
-
Idempotent seeds in Elixir
To ruin the party, deterministic UUID generation is exactly what UUID v5 is designed for. And since Ecto does not validate UUIDs against their specs, you might as well use uuid again and do:
- Ecto: A toolkit for data mapping and language integrated query
-
Sketch of a Post-ORM
To me this looks a lot like ecto https://github.com/elixir-ecto/ecto
Is there a significant difference?
-
Dependency inversion on Elixir using Ports and Adapters design pattern
Ecto database driver use-case
-
Do I need to use Elixir from Go perspective?
When it comes to building microservices, Go has the advantage of being easier to deploy and tighter integration with gRPC. On the other hand, Elixir will provide a more expressive layer to communicate with the database through Ecto.
-
Ask HN: Is my software stack choice sound?
May I ask why CouchDB though? Is it for the offline support?
Phoenix comes with its own database tool called Ecto[0] which is excellent, and it uses Postgres by default. If you're not intended to leverage CouchDB for offline support you should go Postgres without a second thought.
That said, I'm also curious about how to implement offline support with Phoenix in a nice and trivial way.
[0] https://github.com/elixir-ecto/ecto
-
Do it to learn Elixir
The best would be to set aside at least 40 minutes of study a day. Being 20 minutes focused on the core of the language, solving problems and a website that can help you a lot and exercism. Another 20 minutes some of the core frameworks like: Phoenix, Ecto, Enum
-
Using CQRS in a simple Phoenix API with Commanded
This is a testiment to the value and productivity of Phoenix, but the resulting code is just basic CRUD. The views are tied 1:1 with their database-backed Ecto schemas. One thing to note is that Phoenix generates DDD-style contexts. This is unlike Rails, which would produce a typical ActiveRecord sprawl: bloated models directly being accessed and lazily queried across the entire application.
-
How to Use Macros in Elixir
Ecto uses prewalk to count the number of interpolations within a given expression.
-
Dynamic Queries in Ecto (Elixir Lang)
I've used my share of data access libraries and patterns (e.g. hibernate, activerecord, ecto, ...). The only time I've been happy is when I use raw SQL for non-dynamic SQL and a lightweight query builder for everything else.
I feel like I always run into some thing that at best isn't intuitive to express/read and at worse, cannot be expressed. If I remember correctly, when I was learning Elixir/Ecto, https://github.com/elixir-ecto/ecto/issues/1616 issue and the lack of lateral join support caused me issues.
Want to create a user?
"insert into users (id, name, status) values ($1, $2, $3)"
Our query builder takes pretty raw SQL fragments:
q = Query.new()
What are some alternatives?
pure-orm - A pure ORM for writing native SQL queries yielding pure business objects
moebius - A functional query tool for Elixir
pgdbf - Convert XBase / FoxPro databases to PostgreSQL
amnesia - Mnesia wrapper for Elixir.
rusqlite-model - Model trait and derive implementation for rusqlite
postgrex - PostgreSQL driver for Elixir
mammoth - A type-safe Postgres query builder for TypeScript.
couchdb_connector - A couchdb connector for Elixir
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
datomex - Elixir driver for the Datomic REST API
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
riak - A Riak client written in Elixir.