HarisudhanRavi
How best to handle multiple results with Repo.get/3?
I recently saw this YouTube video by a React dev writing a get_by_id function:
He uses findFirst() from some javascript ORM. Even though it’s not an issue, it feels weird to me, because id is usually a primary key in the database and is a unique index. There is no need to use findFirst to query by primary key.
But Ecto handles it differently using Repo.get/3. It throws an exception if there is more than one result which seems to be straightforward.
I am a complete Elixir Dev and have little experience with JS using Vue. I am not sure about ORMs in other languages. Is this a good code using this kind of query by a primary key? How do other languages do this?
PS: I know this is an Elixir form. Since good design patterns is a recent topic in the Elixir community, I thought this would be a place to discuss this.
Most Liked
cmo
There are other options available, e.g. findUniqueOrThrow, which is more akin to Repo.get.
tfwright
Yes I would say this is the better way to implement this kind of API and the JS version is overly defensive and thus simply less correct .
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Practical resources that improve the lives of professional developers.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"