What do we do with the migrations runner in this project?

Hi,
I found this project and thought I could use it in a project of mine if it was up to date. So I am thinking of updating it to the new Ecto. However since this project includes support for migrations I wonder what should I do about them? Should we just delete the support for migrations or should I create a mix tasks for handling them or something? If I understand things correctly the migration related stuff has been moved to ecto_sql.

Thank you for your wonderful adapter! 👍

[madshargreave]

I'm interested in this as well

I'm interested in this as well

In the support of Ecto 3 or in the migrations? I think I am going try to do a pr to fix update to ecto 3 anyway. If you are interested in the support for migrations, I will try to keep them.

I'm interested in this as well

Apparently there is this. I will just use that for my own needs. https://hexdocs.pm/ecto3_mnesia/Ecto.Adapters.Mnesia.html

[AndrewDryga]

@August401 I think migrations are still a nice way to organize your database structure so I would try to keep them, which requires us to write tasks similar to the ones in ecto_sql (unfortunately :().