Understood, not semantics of ecto + db savepoints, just semantics of savepoints. The way we use save points is that we have a special error that we raise during an operation, and if one of those errors is raised only, do we restore a save point. And we release the save point immediately afterwards. So I think we should be alright 
Thanks for the info 
zachdaniel
Creator of Ash
0
kuon
I just want to chime in with a small library I wrote that might help when using transaction instead of multi.
You use it like this:
# create_user, create_billing, create_subscription return {:ok, value}
create_user(args)
|> then_ok(fn user ->
create_billing(user)
end)
|> then_ok(fn billing ->
create_subscription(billing)
end)
or
Flow.start(:user, fn ->
create_user(args)
end)
|> Flow.then_ok(:billing fn %{user: user} ->
create_billing(user)
end)
...
In case of error it returns the same format as multi, {:error, success_steps, error_step_name, error_step_return}
It is similar to using with directly but you can write code inline (which I didn’t do in the above example, so there isn’t that much value.
This library contains helpers I added when I needed them, it doesn’t have a proper “design” from the start, so there might be some inconsistencies.
1
wojtekmach
Hex Core Team
I have created a PR for Repo.transaction_with:
https://github.com/elixir-ecto/ecto/pull/4577
Thanks everyone for feedback, in particular @sasajuric and @tomkonidas for writing about this.
23
wojtekmach
Hex Core Team
lud
Is there any chance that at some point it will support returning :ok from the callback? I’d like to adopt transact instead of the one I rolled out long time ago, but we have a lot of function that do some writes and just return ok.
2
wojtekmach
Hex Core Team