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: docs/guide/topics-migrations.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,3 +30,26 @@ yii mongodb-migrate
30
30
# reverts the last applied migration
31
31
yii mongodb-migrate/down
32
32
```
33
+
## Special configuration for an application that uses more than one DB engine
34
+
35
+
In case your application uses multiple databases, example:
36
+
37
+
- MySQL + MongoDB
38
+
39
+
If you run the migration commands, it will evaluate both MySQL and MongoDB migration files at the same time since both by default share the same folder.
40
+
41
+
**Problem: MongoDB will try to run MySQL's migration files and the other way around.**
42
+
43
+
In order to avoid that behavior, you can create a new folder called `mongodb` under your `migrations` folder, and then setup your console application like this:
This directory contains scripts for automated test runs via the [Travis CI](http://travis-ci.org) build service. They are used for the preparation of worker instances by setting up needed extensions and configuring database access.
1
+
This directory contains scripts for automated test runs via the [Travis CI](http://travis-ci.com) build service. They are used for the preparation of worker instances by setting up needed extensions and configuring database access.
2
2
3
3
These scripts might be used to configure your own system for test runs. But since their primary purpose remains to support Travis in running the test cases, you would be best advised to stick to the setup notes in the tests themselves.
0 commit comments