Open FelixZY opened 5 months ago
The reason I noticed this is because I prefer graphile-migrate run ./migrations/current.sql
over watch
as I don't want to run semi-completed statements accidentally. I also don't want to mess with my editor (vscode) to disable auto-save for a single file in my repo.
You should use graphile-migrate watch --once
rather than graphile-migrate run
for your use case.
Summary
I set up a
current.sql
like this:I then tried running
graphile-migrate compile
andgraphile-migrate run
against it but the fixtures do not appear to be substituted in:The fixtures are substituted in correctly when running
graphile-migrate --config src/db/.gmrc commit
Steps to reproduce
See above
Expected results
The fixtures should be substituted in when using
compile
andrun
Actual results
The fixtures are not substituted in when using
compile
andrun
Additional context
OS: dockerized
mcr.microsoft.com/devcontainers/base:bookworm
running on ubuntu 20.0.4graphile-migrate
:2.0.0-rc.2
bun
:1.1.13
Possible Solution
Support fixture substitution in
compile
andrun