migration.md 11.4 KB
Newer Older
Alexander Makarov committed
1 2 3
Database Migration
==================

Larry Ullman committed
4 5
Like source code, the structure of a database evolves as a database-driven application is developed and maintained. For example, during development, a new table may be added; Or, after the application goes live, it may be discovered that an additional index is required. It is important to keep track of these structural database changes (called **migration**), just as changes to the source code is tracked using version control. If the source code and the database become out of sync, bugs will occur, or the whole application might break. For this reason, Yii provides a database migration
tool that can keep track of database migration history, apply new migrations, or revert existing ones.
Alexander Makarov committed
6

Larry Ullman committed
7
The following steps show how database migration is used by a team during development:
Alexander Makarov committed
8

Larry Ullman committed
9 10 11 12
1. Tim creates a new migration (e.g. creates a new table, changes a column definition, etc.).
2. Tim commits the new migration into the source control system (e.g. Git, Mercurial).
3. Doug updates his repository from the source control system and receives the new migration.
4. Doug applies the migration to his local development database, thereby syncing his database to reflect the changes Tim made.
Alexander Makarov committed
13

Larry Ullman committed
14
Yii supports database migration via the `yii migrate` command line tool. This tool supports:
Alexander Makarov committed
15

Larry Ullman committed
16 17 18
* Creating new migrations
* Applying, reverting, and redoing migrations
* Showing migration history and new migrations
Alexander Makarov committed
19 20 21 22

Creating Migrations
-------------------

Larry Ullman committed
23
To create a new migration, run the following command:
Alexander Makarov committed
24

25
```
26
yii migrate/create <name>
27
```
Alexander Makarov committed
28

Larry Ullman committed
29
The required `name` parameter specifies a very brief description of the migration. For example, if the migration creates a new table named *news*, you'd use the command:
Alexander Makarov committed
30

31
```
32
yii migrate/create create_news_table
33
```
Alexander Makarov committed
34

Larry Ullman committed
35 36 37 38 39 40
As you'll shortly see, the `name` parameter
is used as part of a PHP class name in the migration. Therefore, it should only contain letters,
digits and/or underscore characters.

The above command will create a new
file named `m101129_185401_create_news_table.php`. This file will be created within the `protected/migrations` directory. Initially, the migration file will be generated with the following code:
Alexander Makarov committed
41

42
```php
Alexander Makarov committed
43 44 45 46 47 48 49 50 51 52 53 54
class m101129_185401_create_news_table extends \yii\db\Migration
{
	public function up()
	{
	}

	public function down()
	{
		echo "m101129_185401_create_news_table cannot be reverted.\n";
		return false;
	}
}
55
```
Alexander Makarov committed
56

Larry Ullman committed
57 58 59 60 61 62
Notice that the class name is the same as the file name, and follows the pattern
`m<timestamp>_<name>`, where:

* `<timestamp>` refers to the UTC timestamp (in the
format of `yymmdd_hhmmss`) when the migration is created,
* `<name>` is taken from the command's `name` parameter.
Alexander Makarov committed
63

Larry Ullman committed
64 65
In the class, the `up()` method should contain the code implementing the actual database
migration. In other words, the `up()` method executes code that actually changes the database. The `down()` method may contain code that reverts the changes made by `up()`.
Alexander Makarov committed
66

Larry Ullman committed
67 68 69 70
Sometimes, it is impossible for the `down()` to undo the database migration. For example, if the migration deletes
table rows or an entire table, that data cannot be recovered in the `down()` method. In such
cases, the migration is called irreversible, meaning the database cannot be rolled back to
a previous state. When a migration is irreversible, as in the above generated code, the `down()`
Alexander Makarov committed
71 72 73 74
method returns `false` to indicate that the migration cannot be reverted.

As an example, let's show the migration about creating a news table.

75
```php
Alexander Makarov committed
76 77 78 79
class m101129_185401_create_news_table extends \yii\db\Migration
{
	public function up()
	{
Alexander Makarov committed
80
		$this->db->createCommand()->createTable('tbl_news', [
Alexander Makarov committed
81
			'id' => 'pk',
82
			'title' => 'string(128) NOT NULL',
Alexander Makarov committed
83
			'content' => 'text',
Alexander Makarov committed
84
		])->execute();
Alexander Makarov committed
85 86 87 88 89 90 91
	}

	public function down()
	{
		$this->db->createCommand()->dropTable('tbl_news')->execute();
	}
}
92
```
Alexander Makarov committed
93 94 95 96

The base class [\yii\db\Migration] exposes a database connection via `db`
property. You can use it for manipulating data and schema of a database.

97 98 99 100 101 102 103
The column types used in this example are abstract types that will be replaced
by Yii with the corresponding types depended on your database management system.
You can use them to write database independent migrations.
For example `pk` will be replaced by `int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY`
for MySQL and `integer PRIMARY KEY AUTOINCREMENT NOT NULL` for sqlite.
See documentation of [[QueryBuilder::getColumnType()]] for more details and a list
of available types. You may also use the constants defined in [[\yii\db\Schema]] to
104
define column types.
105 106


Alexander Makarov committed
107 108 109 110 111 112 113 114 115 116 117
Transactional Migrations
------------------------

While performing complex DB migrations, we usually want to make sure that each
migration succeed or fail as a whole so that the database maintains the
consistency and integrity. In order to achieve this goal, we can exploit
DB transactions.

We could explicitly start a DB transaction and enclose the rest of the DB-related
code within the transaction, like the following:

118
```php
Alexander Makarov committed
119 120 121 122 123 124 125
class m101129_185401_create_news_table extends \yii\db\Migration
{
	public function up()
	{
		$transaction=$this->getDbConnection()->beginTransaction();
		try
		{
Alexander Makarov committed
126
			$this->db->createCommand()->createTable('tbl_news', [
Alexander Makarov committed
127 128 129
				'id' => 'pk',
				'title' => 'string NOT NULL',
				'content' => 'text',
Alexander Makarov committed
130
			])->execute();
Alexander Makarov committed
131 132 133 134 135 136 137 138 139 140 141 142
			$transaction->commit();
		}
		catch(Exception $e)
		{
			echo "Exception: ".$e->getMessage()."\n";
			$transaction->rollback();
			return false;
		}
	}

	// ...similar code for down()
}
143
```
Alexander Makarov committed
144 145 146 147 148 149 150 151 152 153 154 155 156

> Note: Not all DBMS support transactions. And some DB queries cannot be put
> into a transaction. In this case, you will have to implement `up()` and
> `down()`, instead. And for MySQL, some SQL statements may cause
> [implicit commit](http://dev.mysql.com/doc/refman/5.1/en/implicit-commit.html).


Applying Migrations
-------------------

To apply all available new migrations (i.e., make the local database up-to-date),
run the following command:

157
```
158
yii migrate
159
```
Alexander Makarov committed
160 161 162 163 164 165 166 167 168 169 170 171 172 173

The command will show the list of all new migrations. If you confirm to apply
the migrations, it will run the `up()` method in every new migration class, one
after another, in the order of the timestamp value in the class name.

After applying a migration, the migration tool will keep a record in a database
table named `tbl_migration`. This allows the tool to identify which migrations
have been applied and which are not. If the `tbl_migration` table does not exist,
the tool will automatically create it in the database specified by the `db`
application component.

Sometimes, we may only want to apply one or a few new migrations. We can use the
following command:

174
```
175
yii migrate/up 3
176
```
Alexander Makarov committed
177 178 179 180 181 182

This command will apply the 3 new migrations. Changing the value 3 will allow
us to change the number of migrations to be applied.

We can also migrate the database to a specific version with the following command:

183
```
184
yii migrate/to 101129_185401
185
```
Alexander Makarov committed
186 187 188 189 190 191 192 193 194 195 196 197 198 199

That is, we use the timestamp part of a migration name to specify the version
that we want to migrate the database to. If there are multiple migrations between
the last applied migration and the specified migration, all these migrations
will be applied. If the specified migration has been applied before, then all
migrations applied after it will be reverted (to be described in the next section).


Reverting Migrations
--------------------

To revert the last one or several applied migrations, we can use the following
command:

200
```
201
yii migrate/down [step]
202
```
Alexander Makarov committed
203 204 205 206 207 208 209 210 211 212 213 214 215 216

where the optional `step` parameter specifies how many migrations to be reverted
back. It defaults to 1, meaning reverting back the last applied migration.

As we described before, not all migrations can be reverted. Trying to revert
such migrations will throw an exception and stop the whole reverting process.


Redoing Migrations
------------------

Redoing migrations means first reverting and then applying the specified migrations.
This can be done with the following command:

217
```
218
yii migrate/redo [step]
219
```
Alexander Makarov committed
220 221 222 223 224 225 226 227 228 229 230

where the optional `step` parameter specifies how many migrations to be redone.
It defaults to 1, meaning redoing the last migration.


Showing Migration Information
-----------------------------

Besides applying and reverting migrations, the migration tool can also display
the migration history and the new migrations to be applied.

231
```
232 233
yii migrate/history [limit]
yii migrate/new [limit]
234
```
Alexander Makarov committed
235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250

where the optional parameter `limit` specifies the number of migrations to be
displayed. If `limit` is not specified, all available migrations will be displayed.

The first command shows the migrations that have been applied, while the second
command shows the migrations that have not been applied.


Modifying Migration History
---------------------------

Sometimes, we may want to modify the migration history to a specific migration
version without actually applying or reverting the relevant migrations. This
often happens when developing a new migration. We can use the following command
to achieve this goal.

251
```
252
yii migrate/mark 101129_185401
253
```
Alexander Makarov committed
254

255
This command is very similar to `yii migrate/to` command, except that it only
Alexander Makarov committed
256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294
modifies the migration history table to the specified version without applying
or reverting the migrations.


Customizing Migration Command
-----------------------------

There are several ways to customize the migration command.

### Use Command Line Options

The migration command comes with four options that can be specified in command
line:

* `interactive`: boolean, specifies whether to perform migrations in an
  interactive mode. Defaults to true, meaning the user will be prompted when
  performing a specific migration. You may set this to false should the
  migrations be done in a background process.

* `migrationPath`: string, specifies the directory storing all migration class
  files. This must be specified in terms of a path alias, and the corresponding
  directory must exist. If not specified, it will use the `migrations`
  sub-directory under the application base path.

* `migrationTable`: string, specifies the name of the database table for storing
  migration history information. It defaults to `tbl_migration`. The table
  structure is `version varchar(255) primary key, apply_time integer`.

* `connectionID`: string, specifies the ID of the database application component.
  Defaults to 'db'.

* `templateFile`: string, specifies the path of the file to be served as the code
  template for generating the migration classes. This must be specified in terms
  of a path alias (e.g. `application.migrations.template`). If not set, an
  internal template will be used. Inside the template, the token `{ClassName}`
  will be replaced with the actual migration class name.

To specify these options, execute the migrate command using the following format

295
```
296
yii migrate/up --option1=value1 --option2=value2 ...
297
```
Alexander Makarov committed
298 299 300 301 302

For example, if we want to migrate for a `forum` module whose migration files
are located within the module's `migrations` directory, we can use the following
command:

303
```
304
yii migrate/up --migrationPath=ext.forum.migrations
305
```
Alexander Makarov committed
306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321


### Configure Command Globally

While command line options allow us to configure the migration command
on-the-fly, sometimes we may want to configure the command once for all.
For example, we may want to use a different table to store the migration history,
or we may want to use a customized migration template. We can do so by modifying
the console application's configuration file like the following,

```php
TBD
```

Now if we run the `migrate` command, the above configurations will take effect
without requiring us to enter the command line options every time.