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
How would you recommend handling when one needs to do slightly different things, like:
1. init migration
2. another
3.A sql-server specific version
3.B postgres version
This hasn't come up for me with goose but was an issue I had in a previous job. one thing that comes to mind is similar to how you handle restricting which db providers. maybe a compile time flag that selects which version of 3 to use? but that would only work for a new binary for each db. maybe a goose annotation goose up oracle, goose up sqlite or something? (one big file for version 3, but there might be goose up (universal stuff) then goose up postgres specific then goose up universal again, then goose down universal then goose down postgres specific, as an example)
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
-
How would you recommend handling when one needs to do slightly different things, like:
This hasn't come up for me with goose but was an issue I had in a previous job. one thing that comes to mind is similar to how you handle restricting which db providers. maybe a compile time flag that selects which version of 3 to use? but that would only work for a new binary for each db. maybe a goose annotation goose up oracle, goose up sqlite or something? (one big file for version 3, but there might be goose up (universal stuff) then goose up postgres specific then goose up universal again, then goose down universal then goose down postgres specific, as an example)
Beta Was this translation helpful? Give feedback.
All reactions