@LostKobrakai Awesome, thanks for that! It seems the readme makes clear everything I’d need to do and how it works except for one big thing, the multiple database calls across the multiple databases do they run in a singular DB transaction each across them all or are they on a call-by-call basis only (I.E. no DB transactions across the entire Sage call)? I.E. does it start up an Ecto.Repo.transaction for all calls to the given database (thus those calls need to be handled inside that transaction) on the first call of a given repo’s transaction or…)? How does it handle the transactions failing in any order and handling the rollback then?
OvermindDL1
LostKobrakai
I’ve never used it by myself, so I’m not sure how integrated it is with ecto. But maybe the possibility to arbitrarily nest transactions in ecto can be of aid for that.
0
OvermindDL1
That depends on the database itself, but that’s not the issue here, the issue is keeping two transactions active and in sync across two different databases, I.E. two different Repo modules.
0
LostKobrakai
I was thinking about something like this, but as I said I’ve no clue if it would really work:
Repo1.transaction(fn ->
Repo2.transaction(fn ->
Sage.execute(…)
end)
end)
Maybe there are also better ways to do that.
2