File tree Expand file tree Collapse file tree 2 files changed +8
-8
lines changed
user_guide_src/source/dbmgmt Expand file tree Collapse file tree 2 files changed +8
-8
lines changed Original file line number Diff line number Diff line change @@ -122,14 +122,11 @@ class MigrationRunner
122
122
protected $ groupSkip = false ;
123
123
124
124
/**
125
- * Constructor.
125
+ * The migration can manage multiple databases. So it should always use the
126
+ * default DB group so that it creates the `migrations` table in the default
127
+ * DB group. Therefore, passing $db is for testing purposes only.
126
128
*
127
- * When passing in $db, you may pass any of the following to connect:
128
- * - group name
129
- * - existing connection instance
130
- * - array of database configuration values
131
- *
132
- * @param array|ConnectionInterface|string|null $db
129
+ * @param array|ConnectionInterface|string|null $db DB group. For testing purposes only.
133
130
*
134
131
* @throws ConfigException
135
132
*/
Original file line number Diff line number Diff line change @@ -66,7 +66,7 @@ Database Groups
66
66
===============
67
67
68
68
A migration will only be run against a single database group. If you have multiple groups defined in
69
- **app/Config/Database.php **, then it will run against the ``$defaultGroup `` as specified
69
+ **app/Config/Database.php **, then by default it will run against the ``$defaultGroup `` as specified
70
70
in that same configuration file.
71
71
72
72
There may be times when you need different schemas for different
@@ -79,6 +79,9 @@ match the name of the database group exactly:
79
79
80
80
.. literalinclude :: migration/003.php
81
81
82
+ .. note :: The **migrations** table that tracks which migrations have already been
83
+ run will be always created in the default database group.
84
+
82
85
Namespaces
83
86
==========
84
87
You can’t perform that action at this time.
0 commit comments