You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've got a weird situation. The following happens for every developer in my team, except for me. The patches work fine on my installation.
This patch or anything really, doesn't really matter, won't apply, but the down statement will execute (even though the file isn't in the gorp_migrations table [1])
Background info
Postgres backend
Latest sql-migrate release
The sql-migrate binary is distributed as part of the repository all migrations are in. People simply re-use the bundled (stand-alone) binary
We have multiple migrations directories.
Everything works fine when creating a new database, all patches work as intended.
The patch
It can be anything really, doesn't really matter. Single lines, no lines, without statement start/end tags, doesn't make a difference.
Hi.
We've got a weird situation. The following happens for every developer in my team, except for me. The patches work fine on my installation.
This patch or anything really, doesn't really matter, won't apply, but the down statement will execute (even though the file isn't in the
gorp_migrations
table [1])Background info
migrations
directories.The patch
It can be anything really, doesn't really matter. Single lines, no lines, without statement start/end tags, doesn't make a difference.
The sql-migrate up dtruss output
Command:
sudo dtruss ../sql-migrate up
The sql-migrate down dtruss output
Questions:
down
statement issued when the file isn't applied in the first place.up
statement apply..The text was updated successfully, but these errors were encountered: