The only reason I did not announce I am stepping down from Ecto is because it still has to be maintained until said parties step up. But if you feel like that is not necessary, I am ok with not having to maintain it either.
No, it is not possible yet, as we are collecting feedback from people building stuff using the private APIs - which is not ideal and it will break but at least it is possible. If you can start a new topic here, explaining what you are doing right now, the pros and cons, it can help push the conversation forward. I believe @talentdeficit is interested on this too. This particular item is work that has not been finalized yet.
Ah never mind, I’ve figured it out. From the Ecto 3 Changelog:
Running migrations will now lock the migrations table, allowing you to concurrently run migrations in a cluster without worrying that two servers will race each other and run migrations twice.
In order for this safer migration mechanism to work, at least two database connections are necessary when migrating. One is used to lock the “schema_migrations” table and the other one to effectively run the migrations.