How to safely handle related database operations with Ecto Multi
Join Elixir newsletter
Subscribe to receive Elixir news to your inbox every two weeks.
Expand your skills
Download free e-books, watch expert tech talks, and explore open-source projects. Everything you need to grow as a developer - completely free.
Sometimes you need to do some database operations at once. A simple example: User-A transfers money to User-B. Updating just one balance at the time creates a risk of data desynchronization. What if the first DB operation goes well but updating the second user’s data fails? Sounds like a hard to catch vulnerability.
Fortunately, the IT environment knows the solution. Transaction processing divides the problem into smaller chunks. Every operation is considered separately, but all of them must succeed to apply changes. In that case, User-A won't lose money if the operation of updating User-B balance fails.
Let’s take a look at the code:
Ecto.Multi.new()
|>Ecto.Multi.update(:payer, payer_changeset)
|>Ecto.Multi.update(:reciever, reciever_changeset)
|>Repo.transaction()Atom argument - in update function - is just the name of the operation. It could be anything that is unique among these actions.
Of course, it would be also nice to handle result:
In case of success there will be returned tuple with :ok atom and instead of the updated structure as the second variable, you can expect the map with all updated structures.
Failure brings some helpful information too – like which operation failed (returns its unique atom), what is the failed value, and what has been changed so far (however not applied).
More about Ecto.Multi: https://hexdocs.pm/ecto/Ecto.Multi.html
Related posts
Dive deeper into this topic with these related posts
You might also like
Discover more content from this category
There is a common scenario: You'd like to debug your Phoenix app with break!/4 or IEx.pry/0. Everything works fine, until... Phoenix server throws a timeout error statement.
Ensuring that GraphQL mutations properly update your Apollo client's cache can be a bit tricky - here's how to manually control that.
With pure function React Components you're not allowed to use lifecycle methods like componentDidMount or componentWillUnmount.