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
In production environments, database access is often restricted and developers don’t necessarily have rights to execute DDL commands (i.e. CREATE, ALTER, DROP, etc. statements). In such cases, migrations can be executed as follows:
81
81
82
-
1. Create the `<plugin_name>_schema_history` table manually by running the following SQL statements:
82
+
1. *Create the `<plugin_name>_schema_history` table manually:*
83
83
+
84
84
[source, sql]
85
85
----
@@ -102,9 +102,9 @@ insert into <plugin_name>_schema_history (installed_rank, version, description,
102
102
----
103
103
+
104
104
Ensure that you replace `<plugin_name>` with the name of a plugin like `analytics`.
105
-
+
106
-
2. *Run a Dry Run (if needed for review before applying migrations):*
107
105
106
+
2. *Run a Dry Run (if needed for review before applying migrations):*
107
+
+
108
108
Flyway CLI does not support dryRun directly, but you can use `-outputType=json` to review pending migrations:
flyway -url=jdbc:mysql://127.0.0.1:3306/killbill -user=root -password=password -locations=filesystem:C:/var/migrations info -outputType=json
119
118
----
120
-
119
+
+
121
120
This will generate a JSON output similar to the following, which includes details such as the migration version, description, and the file path containing the SQL queries that will be executed:
122
-
121
+
+
123
122
[source, bash]
124
123
----
125
124
{
@@ -180,5 +179,5 @@ This will generate a JSON output similar to the following, which includes detail
0 commit comments