Repository navigation
Replies: 1 comment
|
That's not how SQL migration works. You go up/down in version. You can run migration up to a given version. If you want to run a specific SQL file, then just run the SQL on your given DB. You don't need goose for that. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi - I want to specify the schema which my migrations file should be run in. I can't see a way to do that - is there one that I am missing?
I know how to see the versions table etc so I can get the history table in other schemas ok but I can't see a way to specify a schema so my SQL will be run within it. (something like a function call to set a search path). I could do this manually if the Up call supported a transaction but it doesn't appear to?
(Use case is multi tenancy and schema per tenant - I have seen a similar question asked but no answer.)
Thanks
All reactions