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
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,7 @@ Options:
122
122
-ssl-key string
123
123
file path to SSL key in pem format (only support on mysql)
124
124
-table string
125
-
migrations table name (default "goose_db_version")
125
+
migrations table name (default "goose_db_version"). If you use a schema that is not `public`, you should set `schemaname.goose_db-version` when running commands.
126
126
-timeout duration
127
127
maximum allowed duration for queries to run; e.g., 1h13m
128
128
-v enable verbose mode
@@ -300,6 +300,9 @@ Both Up and Down migrations within this file will be run without transactions.
300
300
By default, SQL statements are delimited by semicolons - in fact, query statements must end with a
301
301
semicolon to be properly recognized by goose.
302
302
303
+
By default, all migrations are run on the public schema. If you want to use a different schema,
304
+
specify the schema name using the table option like `-table='schemaname.goose_db_version`.
305
+
303
306
More complex statements (PL/pgSQL) that have semicolons within them must be annotated with `--
304
307
+goose StatementBegin` and `-- +goose StatementEnd` to be properly recognized. For example:
0 commit comments