Doctrine2 Migration Using DBAL instead of $this-addSql

Question

So I've done a bunch of Doctrine2 migrations (https://github.com/doctrine/migrations) but I have a question for a new migration I'm trying to do. I've been digging into the library a little and I see that `$this->addSql()` is used to build a list of SQL to execute and then it gets executed later. I wanted to do something where I select some data, iterate over the rows, insert new data based on that, and then delete the data I selected. This lends itself to the DBAL library pretty easily, but I'm wondering, can I use the `protected $connection` in a migration safely? Or is that bad because it would execute statements before any of my `$this->addSql()` SQL gets executed? Also it seems like this would break the `dry-run` setting from what I've seen in the code. Has anyone had any experience with this type of migration? Are there any best practices? The following is the migration I want to do, but I'm not confident that this is supported by Doctrine Migrations: ``` public function up(Sche…

Accepted Answer

You can use the `$connection` like this

```
$result = $this->connection->fetchAssoc('SELECT id, name FROM table1 WHERE id = 1');
$this->abortIf(!$result, 'row with id not found');
$this->abortIf($result['name'] != 'jo', 'id 1 is not jo');
// etc..
```

You should only read the database and not use the connection to make update/delete so it won't break the dry-run option.

In your example, you should do two migrations. The first will do the two alter table. The second will do the "images with a scrape and convert the scrape to an enclosure" routine. Using multiple migration is easier to revert them if something goes wrong.

Doctrine2 Migration Using DBAL instead of $this->addSql

Solution

Problem