I’ve pushed something to ash_postgres main to address this.
zachdaniel
Creator of Ash
sezaru
Thanks @zachdaniel , now the migration is perfert!
Also, just in case someone wants to do something similar to this, this is the code I’m using to actually run the up and down variables generated from the code:
import Ecto.Migration
args = {self(), Repo, Repo.config(), nil, :forward, :down, %{level: :info, sql: true}}
{:ok, runner} =
DynamicSupervisor.start_child(Ecto.MigratorSupervisor, {Ecto.Migration.Runner, args})
Ecto.Migration.Runner.metadata(runner, [])
# NOTE: This will run the down migration
Code.eval_string(down, [], __ENV__)
Ecto.Migration.Runner.flush()
# NOTE: This will run the up migration
Code.eval_string(up, [], __ENV__)
Ecto.Migration.Runner.flush()
Agent.stop(runner)
1