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 screwed up our production launch and had to manually apply migration files without using sqlx. Now the sqlx::migrate!() macro doesn't work because the _sqlx_migrations tables believes that migrations that have been applied manually haven't been applied. What's the correct way to add these migrations to this metadata table so future migrations can be ran through sqlx?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We screwed up our production launch and had to manually apply migration files without using sqlx. Now the
sqlx::migrate!()
macro doesn't work because the_sqlx_migrations
tables believes that migrations that have been applied manually haven't been applied. What's the correct way to add these migrations to this metadata table so future migrations can be ran through sqlx?Beta Was this translation helpful? Give feedback.
All reactions