Doctrine_manual-1-2-en

Chapter 24: Migrations 330
$migration = new Doctrine_Migration('migrations');
$migration->migrate(0);
Now run the migrate.php script:
Listing
24-13
$ php migrate.php
If you look in the database now, everything we did in the up() methods has been reversed by
the contents of the down() method.
Available Operations
Here is a list of the available methods you can use to alter your database in your migration
classes.
Create Table
Listing
24-14
// ...
public function up()
{
$columns = array(
'id' => array(
'type' => 'integer',
'unsigned' => 1
'notnull' => 1
'default' => 0
),
'name' => array(
'type' => 'string',
'length' => 12
),
'password' => array(
'type' => 'string',
'length' => 12
)
);
$options = array(
'type' => 'INNODB',
'charset' => 'utf8'
);
}
// ...
$this->createTable('table_name', $columns, $options);
You might notice already that the data structures used to manipulate the your schema are
the same as the data structures used with the database abstraction layer. This is because
internally the migration package uses the database abstraction layer to perform the
operations specified in the migration classes.
Drop Table
Listing
24-15
// ...
public function down()
----------------- Brought to you by