doodloo
I’m trying to make sense of something and the fact that I don’t understand it might prove that I’m using it wrong.
I’ve got various changeset functions exposed for an Ecto Schema. They add an optimistic lock check to the changeset structs.
As part of a large Ecto Multi, I noticed that when the update fails because of a lock mismatch, an exception is raised rather than an error tuple.
This kind of defeats the purpose of using an Ecto Multi in the first place, as the goal is to have the result of multi |> Repo.transaction() piped into a case statement, to gracefully let the user know what’s happening.
What is wrong in my logic?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
So the issue with optimistic locks is that you don’t get to know that the lock field was the actual issue causing the more general error of trying to update a stale record. E.g. the original record could’ve been deleted in the meantime as well. So the changeset functionality around
optimistic_lockcannot handle the resulting error. There is astale_error_fieldconfig onRepo.updatethough, which you can use to catch the exception and instead have it reported as an error.doodloo
Thanks a lot @LostKobrakai . Sorry for the late answer!