fix: refs #7759 Change order of myt-run execution

myt-run.js

@@ -149,6 +149,17 @@ class Run extends Command {
             await server.wait();
             const conn = await myt.createConnection();
 
+            // Apply changes
+
+            const hasTriggers = await fs.exists(`${dumpDataDir}/triggers.sql`);
+
+            Object.assign(opts, {
+                triggers: !hasTriggers,
+                commit: true,
+                dbConfig
+            });
+            await myt.run(Push, opts);
+
             // Mock date functions
 
             this.emit('mockingDate');
@@ -163,17 +174,6 @@ class Run extends Command {
                 await connExt.multiQuery(conn, sql);
             }
 
-            // Apply changes
-
-            const hasTriggers = await fs.exists(`${dumpDataDir}/triggers.sql`);
-
-            Object.assign(opts, {
-                triggers: !hasTriggers,
-                commit: true,
-                dbConfig
-            });
-            await myt.run(Push, opts);
-
             // Apply fixtures
 
             this.emit('applyingFixtures');

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@verdnatura/myt",
-  "version": "1.6.12",
+  "version": "1.6.13",
   "author": "Verdnatura Levante SL",
   "description": "MySQL version control",
   "license": "GPL-3.0",